implement-feature

To turn an approved OpenSpec proposal into a pull request, this Skill automates code generation, worktree setup, quality validation, and PR creation. It selects an execution tier based on coordinator availability and commits the implementation for review.

Worktree management for parallel feature implementation sets up isolated feature branches automatically. The Skill resolves branch handling and selects local-parallel, coordinated, or sequential execution tiers based on your environment's coordinator availability.

Yes, you can automate tests and linting before opening a pull request. The Skill runs built-in validation and quality gates, including contract checks, on the generated code changes before committing the implementation as a PR.

The best way to manage sequential execution tiers for OpenSpec change IDs is through automated tier selection. The Skill evaluates coordinator availability and dynamically assigns coordinated, local-parallel, or sequential modes to handle the implementation workflow.

Yes, you need an approved OpenSpec change ID before starting automated feature implementation. The Skill specifically targets approved OpenSpec proposals within a repository to generate the necessary code changes and open a review-ready pull request.

Automated PR creation waits for review after committing the implementation to ensure code quality oversight. After passing validation gates and contract checks, the changes are submitted as a pull request rather than merging directly to the main branch.