メニュー
Phase 4 of the SRS workflow. Reads spec.md and writes one detailed plan file per SRS section (§1–§3 + Appendices). Each file is a complete blueprint for the corresponding SRS section. No word limit.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | sr-plan |
| description | Phase 4 of the SRS workflow. Reads spec.md and writes one detailed plan file per SRS section (§1–§3 + Appendices). Each file is a complete blueprint for the corresponding SRS section. No word limit. |
Goal: produce 12 plan files — one per SRS section — that serve as unambiguous blueprints for SRS generation. No summarizing, no truncation.
Ask the user: "Which project should I plan? (slug)"
Read projects/{slug}/spec.md. If missing, tell user to run $sr-spec first.
Load .cursor/skills/srs-workflow/references/plan-structure-guide.md.
Create all files under projects/{slug}/plan/. For each file, follow the detailed
spec in plan-structure-guide.md for what must be included.
Write in this order (each file before proceeding to next):
00-overview.md — master map, FR/NFR count totals, actor table, assumptions01-introduction.md — §1.1 Purpose, §1.2 Scope (IN/OUT table), §1.3 Definitions, §1.4 References, §1.5 Overview02-overall-description.md — §2.1 Perspective, §2.2 Functions, §2.3 User Characteristics, §2.4 Constraints, §2.5 Assumptions, §2.6 Apportioning03-01-external-interfaces.md — UI screens, hardware, software APIs, communication protocols03-02-functional-requirements.md — ALL FRs with "shall" stubs + GWT stubs + priority03-03-performance.md — ALL NFRs with numeric Response Measure or [TBD]03-04-database.md — entities, retention, volumes, PII fields03-05-design-constraints.md — imposed tech stack, compliance-driven constraints03-06-system-attributes.md — reliability, availability, security, maintainability, portability, usability03-07-other-requirements.md — i18n, legal, operational, transition, trainingappendix-a-glossary.md — all domain terms needing precise definitionsappendix-b-open-issues.md — every [NEEDS USER INPUT] from all plan files, with owner + resolve-byFR numbering rules (enforced across all plan files):
FR-NN [Essential|Conditional|Optional][NEEDS USER INPUT: {specific question}]After all 12 files are written, run:
python .cursor/scripts/plan_validator.py --dir projects/{slug}/plan/ --stats
Use its counts (don't recount by hand — for large plans manual counting drifts).
Output:
| File | Section | FRs | NFRs | Open items |
|------|---------|-----|------|-----------|
| 00-overview.md | Master map | — | — | {n} |
| 03-02-functional-requirements.md | §3.2 FR | {n} | — | {n} |
...
Total: {FR count} FRs ({Essential}/{Conditional}/{Optional})
{NFR count} NFRs ({confirmed} confirmed / {TBD} [TBD])
{open} open items → see appendix-b-open-issues.md
Ask the user:
"Plan is ready. What would you like to do?
A) Approve → proceed to $sr-generate
B) Modify a section → which file(s)?
C) Show a plan file → which one?
D) Add features → run $sr-brainstorm again to extend"
If B: update the relevant file(s) and return to Step 3.
If C: display the file content, then return to Step 3.
If D: instruct user to run $sr-brainstorm and update spec, then restart from Step 0.
If A: proceed.
Output when plan is approved:
Plan approved.
Files: projects/{slug}/plan/ (12 files)
FRs planned: {total} ({Essential} Essential / {Conditional} Conditional / {Optional} Optional)
NFRs planned: {total}
Open items: {count}
Next: $sr-generate → generates full SRS from this plan (no word limit)
Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.
Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.
Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).
Create a machine-readable phased JSON plan bundle from a spec or feature description. Produces a compact master manifest plus per-phase step files for resumable ck:cook execution.
Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.