From plan
Creates implementation plan spec files for features, bugs, and chores. Use when user asks to plan a feature, fix a bug, or handle a chore, or when creating a spec/implementation document.
npx claudepluginhub andercore-labs/claudes-kitchen --plugin planThis skill uses the workspace's default tool permissions.
| Type | Args | Output | Jira |
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
| Type | Args | Output | Jira |
|---|---|---|---|
| feature | description | specs/{name}.md | No |
| feature_rfc | ticket desc | specs/feature-{ticket}-{name}.md | Optional |
| bug | app ticket desc | apps/{app}/specs/bug-{ticket}-{name}.md | Yes |
| chore | description | specs/{name}.md | No |
| Use feature_rfc when | Use feature when |
|---|---|
| Cross-team / cross-layer impact | Single layer, low blast radius |
| High risk or regulatory concern | Low risk, familiar pattern |
| Data migration required | No schema changes |
| Unknown failure modes | Well-understood solution space |
bug → root cause known or unknown, regression risk chore → tech debt, config, non-functional work
1. Read README.md → project context
2. Research codebase → existing patterns + exact files
3. Create spec → replace ALL <placeholders>
4. Report → relative path only
Phase 0 — Reason (before any research):
Decompose → smallest independent units + hard deps
Architecture fit → existing patterns + blast radius
Risk surface → 3 failure modes + unknowns
Test strategy → define "done" observably before solution
Minimal footprint → smallest change delivering full value
→ Document output in plan's ## Reasoning Notes section.
Phase 1 — Research (exact order):
1. README.md
2. app/server/** → layers, patterns, entry points
3. app/client/** → components, state, routing
4. 2 similar existing implementations
5. Exact files to change (specific, not approximate)
Step 1: Validate Jira ticket → abort if invalid (use workflows:jira-recipe)
Step 2: Fetch ticket details → abort if missing
Step 3: Research codebase → root cause → surgical fix plan
| Rule | Requirement |
|---|---|
| Atomic | Single focused session |
| Specific | Names exact files + functions |
| Verifiable | "Done when:" observable outcome |
| Ordered | No task depends on later task |
| Tested | Each functional task paired with test |
| Type | Scope |
|---|---|
| feature | Follow existing patterns; no new abstractions unless unavoidable |
| feature_rfc | Same + atomic tasks + rollback strategy |
| bug | Minimal changes; root cause only; no scope creep |
| chore | Simple + thorough; prevent second round of changes |
UI/interaction changes → add early task:
Create: {project-e2e-dir}/test_{name}.md
Ref: project's existing E2E test files
Add to: Relevant Files → New Files
Add to: Validation Commands
New library → {pkg-manager} add {pkg} → document in Notes
See formats.md for complete templates.
feature:
Description → User Story → Problem → Solution
Relevant Files → Implementation Plan (3 phases)
Tasks → Testing → Acceptance Criteria → Validation → Notes
feature_rfc adds over feature:
+ Reasoning Notes (Phase 0 output)
+ Architecture Analysis
+ Risk Assessment
+ Open Questions
+ Rollback Strategy
Tasks: must satisfy all 5 Task Quality rules
bug:
Description → Problem → Solution → Steps to Reproduce
Root Cause Analysis → Relevant Files → Tasks
Acceptance Criteria → Validation → Notes
chore:
Description → Relevant Files → Tasks → Validation → Notes
| Phase | Action |
|---|---|
| 1. Execute | Create spec file |
| 2. Validate | Review against checklist |
| 3. Report | ✓ ALL pass → Proceed | ✗ ANY fail → List violations |
| 4. Fix | Violations → fix → re-validate |
| 5. Store Metrics | ALL pass → mcp__agent-orchestrator__store-skill-metrics |
VALIDATE before saving spec:
- [ ] All <placeholders> replaced?
- [ ] Tasks ordered (foundation → specific)?
- [ ] Last task = Run Validation Commands?
- [ ] Validation commands specific and runnable?
- [ ] UI changes → E2E task added?
- [ ] Bug plan → surgical (minimal changes)?
- [ ] feature_rfc → Reasoning Notes present?
- [ ] Bug plan → Acceptance Criteria present?
- [ ] Report = relative path only?
mcp__agent-orchestrator__store-skill-metrics({
sessionId: "[from context]",
skill: "planning-recipe",
initialViolations: N,
iterations: N,
fixesApplied: N,
finalViolations: 0,
validationPassed: true,
durationSeconds: N,
metadata: { planType: "feature|feature_rfc|bug|chore", ticket: "..." }
})