harness:writing-plans

What problem does it solve?

Producing reliable implementations starts with turning a messy spec into a concrete, testable execution plan. This Skill prevents wasted cycles by forcing rigid acceptance-criteria coverage, scoped work boundaries, and bite-sized TDD-ready tasks before any code changes happen.

Core Features & Use Cases

• Acceptance-criteria coverage gate: Reads features.json and ensures every acceptance_criteria entry maps to at least one task in the plan, preventing orphan requirements.
• Scope control: Explicitly avoids tasks that would violate features.json out_of_scope constraints, including pushing back when a user asks to expand scope.
• Implementation-ready decomposition: Produces a file- and step-specific plan with per-task test commands, code blocks, and commit instructions suitable for agentic or inline execution.
• Architecture decision handling: When a new technical direction emerges during planning, drafts an ADR under docs/decisions/ and references it from the plan.
• Plan persistence conventions: Saves plans to the harness plugin’s canonical docs/plans location (with support for user override) for consistent retrieval across sessions.

Quick Start

Use the harness:writing-plans skill to create an implementation plan for your next feature by giving it the feature spec and asking it to produce a task-by-task plan that covers every acceptance criterion and avoids out_of_scope work.