Implement ADR and Gherkin spec changes into production code with smoke tests.
npx skills add https://github.com/0xdeafcafe/skills --skill implement-change
Please help me install this Agent Skill. Skill: implement-change Source: https://github.com/0xdeafcafe/skills/tree/main/skills/implement-change Command: npx skills add https://github.com/0xdeafcafe/skills --skill implement-change
This Skill helps you move from planning to implementation without losing the intent of the change. It turns an ADR and Gherkin spec into code changes, keeps the work aligned with architectural decisions, and stops at the point where the specified scenarios pass.
Ask the assistant to use implement-change on your ADR and spec so it can plan the diff, confirm the approach, write the code, and run the planned scenarios as smoke tests.
High-intent search queries and answers about installing and using this skill.
To implement code changes from a Gherkin spec and ADR, the Skill reads your architecture decisions and acceptance criteria, proposes a diff plan, and writes production code in logical commits until the specified scenarios pass as smoke tests.
The feature delivery workflow maps touched files and symbol seams from your spec, asks you to confirm the proposed diff plan, writes the code changes, and validates the implementation by running executable scenarios as smoke tests.
You do not strictly need an ADR to generate code from Gherkin acceptance criteria, as a feature spec is mandatory, but an Architecture Decision Record is highly preferred to ensure the generated code follows agreed architectural decisions.
Yes, you can run smoke tests based on Gherkin scenarios without executing the full audit suite. The Skill stops implementation once the planned executable scenarios pass and reports any manual checks still needed.
The best way to align code generation with architectural decisions is to supply an ADR alongside your feature spec. The Skill reads both first, ensuring code follows agreed decisions and maps touched files accordingly before writing logical commits.
Code generation stops before running the full test suite to validate implementation quickly. It runs your spec's executable scenarios as smoke tests to confirm the promised behavior, leaving the comprehensive audit suite for later pipeline execution.
AnExiledDevA user-friendly way to scaffold your next project.
edmundmillerExplain Jujutsu merge semantics, empty merge commits, and conflict resolution.
bdfinstGenerate ATDD Gherkin feature files with a review gate before implementation.
SebastienDegodezWrite BDD scenarios in Gherkin format with domain-aligned language.
