Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Planowanie

pf-plan

/pf-plan

Prowadzi wywiad o wymaganiach produktu, ustala zakres, budżet i metodykę, a potem tworzy brief, architekturę oraz plan MVP.

Repozytorium
atelier ↗
Licencja
MIT
Ostatnia zmiana repozytorium
27.10.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Prowadzi wywiad o wymaganiach produktu, ustala zakres, budżet i metodykę, a potem tworzy brief, architekturę oraz plan MVP.

Wyzwalacze z opisu

plan a product
Oryginalny opis (EN)

The PM / BA / PO stage at the front of the factory: from a short description of what to build, interviews the user for the complete requirement (scope, users, data sensitivity, scale, budget, timeline, team), decides solo vs team lanes and creates them, forecasts a budget under the cost posture (a budget never unlocks paid options), picks a methodology and follows it, writes the product brief, architecture, MVP, stack and budget docs (plus a backlog, sprints and a living dashboard for Agile projects), then hands a ready brief to design. Use when the user says /pf-plan, 'plan a product', 'gathe

Jak działa

  1. 0. Flags
  2. 1. Discovery interview
  3. 2. Solo vs team + create lanes
  4. 3. Budget forecast (cost posture rules, always)
  5. 3b. Platform & stack (best fit, any provider, free-first)
  6. 4. Methodology
  7. 5. Documents
  8. 6. Living dashboard (agile/team only)
  9. 7. Audit, then plan sign-off and hand to design
  10. Never
Sekcje z nagłówków SKILL.md, w oryginale · 45 linii, 880 słów
Podgląd SKILL.md
---
name: pf-plan
description: "The PM / BA / PO stage at the front of the factory: from a short description of what to build, interviews the user for the complete requirement (scope, users, data sensitivity, scale, budget, timeline, team), decides solo vs team lanes and creates them, forecasts a budget under the cost posture (a budget never unlocks paid options), picks a methodology and follows it, writes the product brief, architecture, MVP, stack and budget docs (plus a backlog, sprints and a living dashboard for Agile projects), then hands a ready brief to design. Use when the user says /pf-plan, 'plan a product', 'gather requirements', 'be my PM or BA', 'scope this out', or starts a new product idea and wants it planned before design. Supports --dry-run."
---

# /pf-plan [idea] [--dry-run]

The front of the factory — product manager, business analyst and product owner in one. It turns a rough idea into a complete, costed, lane-planned, methodology-driven plan, then hands a ready brief to `/pf-design`. It **never overrides the cost posture**.

Read first:
- `${CLAUDE_PLUGIN_ROOT}/references/planning.md` (this stage's contract — follow it)
- `${CLAUDE_PLUGIN_ROOT}/references/recommendations.md` (the standing rule for every option this stage offers — platform, stack, methodology, tools: each with pros, cons and cost, and quality/security never traded away for price)
- `${CLAUDE_PLUGIN_ROOT}/references/cost-posture.md` (spend rules — a budget never loosens them)
- `${CLAUDE_PLUGIN_ROOT}/references/platform-selection.md` (pick the best-fit platform/stack, any provider, free-first)
- `${CLAUDE_PLUGIN_ROOT}/references/state-schema.md`

## 0. Flags
`--dry-run`: run the interview and print the plan (requirements, lanes, methodology, budget forecast, doc list) without creating a project or any docs; stop.

## 1. Discovery interview
Per `planning.md` §1: from the idea, ask the missing pieces with AskUserQuestion, a few at a time, skipping anything already given. **At the idea stage, run a quick `swot-analysis`** to surface the risks and opportunities *before* committing effort — it belongs here, early, not right before build (`references/skills.md`). Must end knowing: product + users + the one success outcome; MVP scope; **data sensitivity** (→ `high` if client/financial/personal); scale & audience; any budget and deadline (forecasting only); design direction; team (→ lanes). Working unattended → make the most reasonable assumptions, state them at the top of the plan, and proceed.

## 2. Solo vs team + create lanes
Per `planning.md` §2: recommend solo or a named set of team lanes in one line with the reason (single-surface site → solo; a separable multi-surface product → a lane per surface). On a yes, create them via `/pf-lanes add` and set `pm_lane`. Never over-split. **If the user maintains their own team-lane working standard as a skill, the lanes run inside it — defer to it and its binding team files** (`references/skills.md`); otherwise the factory uses its own built-in lane steps. The factory orchestrates; the user's standard, where present, governs the lane.

## 3. Budget forecast (cost posture rules, always)
Per `planning.md` §3 + `cost-posture.md`: produce the plain forecast — baseline almost always "$0/month on free tiers", a paid line **only** where a real requirement forces it (cheapest that clears the bar, price, trigger), plus a 10x-traffic line. **A stated budget never adds a paid option the project does not need.** Record as `planning.budget_forecast`.

## 3b. Platform & stack (best fit, any provider, free-first)
Per `platform-selection.md`: from the project's real needs, recommend the best-fit **platform + stack** in one plain line with the reason and cost — provider-agnostic (Azure / AWS / GCP / Oracle / Vercel / Cloudflare / Netlify / Render / Fly / open-source self-host / a free static host), **not** an Azure default. Offer 2–3 real alternatives with AskUserQuestion (include Azure, and an open-source/self-host option when it fits), each one line with its trade-off + cost. The user picks. Record `brief.stack` + `brief.deploy_hint` (a target name). This never loosens the cost posture — free-first across every provider, paid only when a real need forces it, on a yes.

## 4. Methodology
Per `planning.md` §4: pick **ship-it** (small/solo), **agile/scrum-lite** (larger/team), or **kanban** (ongoing/maintenance); state which and why; record `planning.methodology`. For agile, break the MVP into user stories grouped into sprints.

## 5. Documents
Per `planning.md` §5 (and `references/skills.md` for which official skill makes each format): create the warranted set as living docs (Claude Docs via the docs connector; Word/PDF/PowerPoint/Excel on request via the docx/pdf/pptx/xlsx skills after the content is settled) — product brief/PRD, architecture overview (with a diagram), MVP definition, stack decision, budget forecast; plus backlog + sprint plan for agile. Size each to the project. Record their links in `planning.documents`.

## 6. Living dashboard (agile/team only)
Per `planning.md` §6: build it as a **published Artifact with the `db` capability** (or the Dashboard type) — published **once**, then updated by **writing rows to its database** (ArtifactData), never by republishing — so progress updates do not re-prompt a page-update approval. Mirror `factory.json` + `lanes/<lane>.json` into its db; the PM and each lane write their status there. Record `planning.dashboard_url`. A solo/small project gets a one-line status in chat instead.

## 7. Audit, then plan sign-off and hand to design
**Before sign-off, audit the plan under different roles** — run **tech-doc-audit** on the architecture + requirements (its 11 expert lenses: director, PO, dev, architect, security, UI/UX, SRE, DevOps, DevSecOps, AI/ML, data/compliance — `references/skills.md`) and fold the gaps in. This is the real pre-build gate — it bakes the audit-under-different-roles discipline into the stage, before a line is built. (SWOT already ran at discovery; escalate to **llmcouncil** only for a genuinely hard fork — not routinely.) Then show the plan (requirements, lanes, methodology, budget forecast, doc links, dashboard). **GATE — plan sign-off:** ask the user to approve or adjust (per `state-schema.md` "Approval words"). On approval: set `gates.plan = "approved"`, write the brief, `log {stage:"plan", event:"approved"}`, and say "Plan approved. Run `/pf-design` — or `/pf-ship` to run the whole pipeline." On changes, revise and re-ask.

## Never
- Suggest a paid option because a budget exists, or otherwise loosen `cost-posture.md`.
- Over-split a solo-sized project into lanes.
- Build the living dashboard by republishing the page on each update — always update its **database** instead.
- Proceed to design before plan sign-off.

Wersje

W bazie nie ma innych skilli o nazwie pf-plan.

Migawka bazy z 13.11.2026 · wersja paczki 6a277e5ca1f1 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90mvp-idea-brief
    Tworzy Idea Brief dla webowego MVP: użytkownik docelowy, problem, obecne obejście, najmniejszy użyteczny rezultat, platforma, budżet i wyłączenia z zakresu.
  • 100build-mvp
    Buduje pełne MVP w repozytorium produktu na podstawie dokumentów specyfikacji i mapy drogowej produktu.
  • 100pm-mvp
    Wyznacza zakres funkcji pierwszej wersji produktu: filtruje listę wymagań pod MVP i określa granice minimalnego produktu.
  • 90mvp-scoping
    Zamienia brief i raport odkrywania w priorytetowy zakres MVP wokół szkieletu działającego scenariusza.
  • 100shape-it
    Zamienia pomysł na produkt, MVP lub funkcję w plan i backlog pionowych plasterków z kryteriami akceptacji.
  • 100story-map
    Buduje mapę historyjek użytkownika z briefu produktu na tablicy Confluence, po przeglądzie zamyka zakres MVP.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.