Generates execution-ready implementation plans from research docs in .artifacts/research/. Ensures junior developers can execute tasks with zero ambiguity. Planning only—no code changes, fixes, or verification.
From harness-engineeringnpx claudepluginhub alchemiststudiosdotai/harness-engineeringThis skill is limited to using the following tools:
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Generate execution-ready, coding-only implementation plans from research documents. The goal is to produce plans that any JR developer can execute immediately with zero ambiguity.
If a JR developer picked this up, could they start coding immediately?
If the answer is "no" or "they'd need to ask clarifying questions," the plan is incomplete.
.artifacts/research/| ❌ DON'T | ✅ DO INSTEAD |
|---|---|
| Fix code issues | Document them as tasks to fix |
| Verify implementations | Plan verification steps |
| Run tests | Plan what tests to write |
| Deploy anything | Plan deployment as a task |
| Make code changes | Document exactly what changes to make |
Read from: .artifacts/research/<topic>.md
Extract: scope, constraints, target files, unresolved questions, proposed solutions
# Capture current state
git rev-parse HEAD # Commit SHA
git status --short # Working tree status
Save as: .artifacts/plan/YYYY-MM-DD_HH-MM-SS_<topic>.md
---
title: "<topic> implementation plan"
link: "<topic>-plan"
type: implementation_plan
ontological_relations:
- relates_to: [[<research-link>]]
tags: [plan, <topic>, coding]
uuid: "<uuid>"
created_at: "<ISO-8601 timestamp>"
parent_research: ".artifacts/research/<file>.md"
git_commit_at_plan: "<short_sha>"
---
## Goal
- ONE singular coding-focused outcome
- Explicitly state what is OUT of scope (ops, deploy, excessive testing)
## Scope & Assumptions
- IN scope: (technical items only)
- OUT of scope: (what we're NOT doing)
- Assumptions: (frameworks, environments, libraries)
## Deliverables
- Source code modules, functions, or APIs
- Documentation limited to developer-level notes (not user docs)
## Readiness
- Preconditions: repos, libs, data schemas, sample inputs
- What must exist before starting
## Milestones
- M1: Skeleton & architecture setup
- M2: Core logic & data flow
- M3: Feature completion & refinement
- M4: Basic test(s) & integration hooks
## Work Breakdown (Tasks)
For EACH task, specify:
- **Task ID**: T001, T002, etc.
- **Summary**: What to do (present tense, actionable)
- **Owner**: who does it
- **Estimate**: time/complexity
- **Dependencies**: other task IDs
- **Target milestone**: M1-M4
- **Acceptance test**: Exactly ONE test that proves it works
- **Files/modules touched**: List exact paths
## Risks & Mitigations
Keep technical:
- Library stability issues
- API version drift
- Schema mismatch risks
- Breaking changes in dependencies
## Test Strategy
At most ONE new test per task, only for validating main coding work.
Focus on proving correctness, not coverage.
## References
- Research doc sections
- Key code references (file:line format)
## Final Gate
- **Output summary**: plan path, milestone count, tasks ready
- **Next step**: proceed to execute-phase with the generated plan path
T003: Add user authentication middleware
- Create src/middleware/auth.ts with verifyToken() function
- Import in src/app.ts and apply to /api/* routes
- Acceptance: curl /api/users returns 401 without header, 200 with valid token
- Files: src/middleware/auth.ts, src/app.ts
- Milestone: M2
T003: Fix auth
- Handle the auth stuff properly
- Make sure it works
Always capture and include:
COMMIT_SHA=$(git rev-parse --short HEAD)
STATUS=$(git status --short)
If research doc mentions specific commits/branches and they've changed:
If planning reveals blockers or prerequisites that need tracking:
Before finalizing, ask:
After plan generation, output:
✓ Plan written to: .artifacts/plan/YYYY-MM-DD_HH-MM-SS_<topic>.md
✓ Milestones: 4
✓ Tasks: 12
✓ Git state: <short_sha>
Next step: Execute phase using the generated plan path
## Task T004: Add rate limiting to API endpoints
**Summary**: Implement token-bucket rate limiting for public API endpoints
**Files**:
- src/middleware/rateLimit.ts (new)
- src/app.ts (modify)
**Changes**:
1. Create src/middleware/rateLimit.ts with TokenBucket class
- Constructor takes capacity and refillRate
- consume(tokens) method returns true if allowed
2. Add rateLimit instance to src/app.ts
3. Apply to /api/public/* routes only
**Acceptance Test**:
- Send 100 requests in 1 second to /api/public/data
- First 60 succeed (200)
- Next 40 fail (429)
- Headers include X-RateLimit-Remaining
**Dependencies**: T001 (Express app setup)
**Milestone**: M2
**Estimate**: 2 hours
Only spawn subagents if:
Typical subagents:
codebase-analyzer: Find where new code fitscontext-synthesis: Extract structured tasks from prose researchDefault: Don't use subagents. Trust the research doc.
After writing the plan document to .artifacts/plan/, proceed to execute-phase if the next step is the Execute phase.