spec

To turn a project brief into an implementation plan, this skill extracts task descriptions, affected files, patterns, and constraints from a search file to define execution order, risk mitigations, and acceptance criteria. It outputs a structured spec document for engineering handoffs.

A software specification document details required modifications, dependencies, acceptance criteria, tests, and documentation requirements. It translates high-level requirements into a precise plan, reducing ambiguity and supporting repeatable planning and auditing across multiple files and teams.

To generate a spec file from a search entry, the skill reads a specified search{id}.md file, extracts implementation strategy details, and writes a standardized spec{id}.md file under the /context/spec directory containing all modifications, phases, and tasks.

Yes, this specification workflow supports planning across multiple files and teams by providing clear Phase and Task delineations. It generates a standardized spec file per search entry to ensure consistent planning, execution order, and auditing.

You define an implementation strategy by extracting constraints, technologies, and patterns from the brief, then mapping out the recommended approach, execution order, and risk mitigations. The resulting spec file explicitly lists all modifications and acceptance criteria.