code

To automate implementing code from a formal software specification, this Skill reads your spec and search context files, maps them to execution phases, and progressively writes code while validating syntax and tests. It updates the spec status based on implementation progress.

Executing a development plan based on spec files requires loading context from search and spec markdown files, performing dependency checks, running validation steps like lint and tests, and refining the output. This process ensures code meets the defined specification requirements.

To validate syntax and tests during iterative spec implementation, the workflow performs prerequisite checks, executes type validation and linting, and runs tests before applying modifications. This continuous validation ensures code quality and prevents regressions throughout the execution phases.

Yes, you need to prepare context files before starting plan execution. The implementation process specifically loads context from /context/search/search{id}.md and /context/spec/spec{id}.md files to map planning context and specifications into actionable development tasks.

A code implementation workflow handles git status and dependency checks by verifying the environment prerequisites before executing plan phases. It ensures dependencies are met and the repository state is clean prior to applying code modifications and validating outputs.

Spec status needs to be updated after implementing code to signal implementation progress and generate accurate reports. Tracking the spec status ensures teams maintain visibility over completion phases, learn from validation failures, and refine the software iteratively.