| name | doc-planning |
| description | Phase 0 (Planning). Use to start documenting a software project or a major initiative - elicit the project charter by asking the SWE about goals, stakeholders, scope, constraints, risks, and success criteria, then generate or update the PM/ planning files. Trigger on "plan a project", "write a charter", "brainstorm scope", "who are the stakeholders", "define scope/risks". |
Doc: Planning (Phase 0)
Elicit and record the project charter. This skill owns Phase 0 only (see LIFECYCLE.md). It asks the SWE about the project, brainstorms scope with them, and writes the planning artifacts. It does NOT analyze requirements or write FRs/UCs - that is doc-analysis / doc-requirements.
Inputs
- The SWE's intent and any seed material (a pitch, a ticket, a system to replace).
- Target project location:
projects/<slug>/PM/ (or repo-root PM/ for the template).
Process (elicitation loop)
- Read any existing
PM/ files and the project slug/DomainCode.
- Ask the SWE a focused batch from the question bank below - group related questions; do not ask one at a time.
- Write answers into the
PM/ files (create from template if missing).
- Re-read what you captured; surface gaps, contradictions, and unstated assumptions; ask a follow-up batch.
- Repeat until the DoD holds. Keep unresolved items as open questions in
PM/Issues.md - do not invent answers.
- Stop at the phase boundary. Hand off an approved, scoped charter to
doc-analysis.
Questions to ask (bank)
- Goal: In one sentence, what will this project deliver, and for whom? What problem does it solve?
- Trigger: Why now? New build, replacement, compliance, scaling, cost?
- Stakeholders: Who is the sponsor? Primary users? SMEs? Who approves / signs off?
- Scope: What is explicitly IN scope? What is explicitly OUT of scope?
- Timeline: Duration, hard deadlines, major milestones?
- Constraints: Budget, team size/skills, mandated tech, regulatory/compliance, integrations?
- Assumptions: What are we assuming is true (access, cooperation, stability)?
- Risks: What could derail this? Likelihood / impact?
- Success: What measurable criteria mean "done and successful"? Key deliverables?
Outputs (creates / updates)
PM/README.md - charter (about, purpose, objectives, scope in/out, constraints, assumptions, success criteria).PM/Stakeholders.md, PM/Milestones.md, PM/Risks.md, PM/Decisions.md, PM/Issues.md.
Definition of Done (gate)
Charter approved; scope in/out stated; stakeholders and risks registered; success criteria measurable. (LIFECYCLE.md Phase 0.)
Handoff
An approved charter + scope boundary. doc-analysis consumes this to bound what gets analyzed. Pass forward: scope statement, package/domain list, known constraints, stakeholder/owner list.
Guardrails
Preserve templates (fill fields, add rows); ASCII only; ask - do not speculate; keep open items explicit. See AGENTS.md.
