02-implement
/02-implement
Implement features, refactors, or bug fixes strictly traceable to an approved specification or issue, enforcing stack-specific engineering standards, living spec synchronization, and automated test verification. Activate when implementing code, fixing bugs, or running /02-implement.
- Author
- bvarnai ↗
- Repository
- agy-standards ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Implement features, refactors, or bug fixes strictly traceable to an approved specification or issue, enforcing stack-specific engineering standards, living spec synchronization, and automated test verification. Activate when implementing code, fixing bugs, or running /02-implement.
Original author description
Implement features, refactors, or bug fixes strictly traceable to an approved specification or issue, enforcing stack-specific engineering standards, living spec synchronization, and automated test verification. Activate when implementing code, fixing bugs, or running /02-implement.
How it works
- Constraints
- Input contract
- Implementation workflows
- Output contract & commit / PR handoff
SKILL.md preview
---
name: 02-implement
description: Implement features, refactors, or bug fixes strictly traceable to an approved specification or issue, enforcing stack-specific engineering standards, living spec synchronization, and automated test verification. Activate when implementing code, fixing bugs, or running /02-implement.
metadata:
lifecycle_stage: "02-implement"
mode: "interactive"
recommended_flags: "--effort medium"
---
# 02 — Spec-driven implementation
## Constraints
- **Tone:** Follow [strict-technical-tone.md](../../fragments/strict-technical-tone.md).
- **Permission:** Create and edit source, test, `docs/spec/`, and user documentation files in CWD that the issue or spec requires.
## Input contract
1. **Source of truth**:
- Require an explicit issue (or `.issue-draft.md` in `CWD`) and/or approved specification in `docs/spec/`. If neither exists, halt and invoke `/01-issue` or `/00-spec` first.
- When `docs/spec/global.md` exists alongside `docs/spec/<unit>.md`, read both `global.md` (for shared architecture, error codes, execution boundaries, and package dependency rules) and the target `<unit>.md` before writing code.
2. **Topic branch check**:
- Inspect `git branch --show-current`. If still on the default branch:
- With `git-brx` on `PATH`: propose `git brx create issue/<id> -y` for a tracked issue. The user confirms or changes the branch type; follow the git-brx skill for everything after that.
- Without `git-brx`: ask how the project creates branches. Do not invent a convention.
## Implementation workflows
### 1. Feature / refactor workflow
1. **Day-0 scaffolding (new repositories only)**: When bootstrapping a brand-new project from `docs/spec/`, initialize standard governance and build files (`LICENSE`, `README.md`, `CHANGELOG.md`, `.gitignore`, `.gitattributes` with `* text=auto eol=lf`, and `.github/workflows/ci.yml`).
2. **Boundary & domain implementation**: Implement narrow execution/runner interfaces (`Runner`, `Inspector`, `HAL`) and core domain logic in small, bisectable units matching the package dependency direction in `global.md`. Update `docs/spec/` and affected user-facing documentation (`README.md`, `docs/user-guide/`) in the same change when CLI flags, configuration keys, or user-visible behaviors change.
3. **Automated tests**: Write unit and black-box verification tests covering every Acceptance Criterion, Edge Case, and Error Matrix row in the spec/issue.
### 2. Bug fix / regression workflow (`fix:`)
1. **Reproduce first (TDD)**: Write a deterministic failing unit or integration test that reproduces the reported bug or edge case before modifying production logic.
2. **Root-cause fix**: Apply the minimal, idiomatic fix at the root cause (avoiding symptom-level workarounds).
3. **Spec check**: If the bug exposed an undocumented invariant or exit code trigger, update `docs/spec/` to lock in the expected behavior.
### 3. Verification gate
- Run the stack's automated test suite and static analysis commands from [`rules/stack-routing.md`](../../rules/stack-routing.md) (`go test -race ./...`, `go vet ./...`, `./mvnw test`, `shellcheck`, `bats`, `ctest`).
- Do not claim completion until all automated tests and linters pass with zero warnings or errors.
## Output contract & commit / PR handoff
Upon passing verification, output:
1. **Acceptance criteria verification matrix**:
| Acceptance criterion / edge case | Status | Verifying test / file |
| :--- | :--- | :--- |
| ... | Pass | `path/to/test_file:TestName` |
2. **Proposed commit** (format from [`rules/git.md`](../../rules/git.md); keep `.issue-draft.md` untracked as the local work-unit spec—update it and notify the user if scope changes mid-flight so the remote issue can be synced, and remove it only after the PR merges; wait for user confirmation before executing mutating Git commands):
```bash
git add <modified-files>
git commit -m "<type>(<component>): <concise summary>"
```
3. **Handoff**: with `git-brx` on `PATH`, continue with the git-brx skill (sync, publish, review). Without it, stop after the commit; the user publishes and opens the PR their own way.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · bvarnai/agy-standards | 100 | MIT |
| ai-driven-dev/framework | 100 | MIT |
Database snapshot: 13.11.2026 · package version 85dd208bf2e0 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95implementation
Implement features with code, tests, and documentation. Use when building features from approved designs following TDD and project coding standards. - 84implement
This skill should be used when the user asks to "implement an issue", "create a PR for issue", "implement issue #123", "turn this issue into code", or wants to implement a GitHub issue following an implementation plan and create a pull request. - 90implement
Execute approved specs, clear tickets, or bounded user requirements as verified repository changes. Use when asked to implement a feature, fix a bug, refactor, migrate, or repair accepted code-review findings. Stops for consequential unresolved requirements or design; does not… - 100forge-implement
Implement a feature or fix from an Issue, plan file, or free-text description, following project standards. Use when the user wants to start working on an Issue, implement a feature, or fix a bug — stops after opening the PR (use forge-ship to also run review). - 100om-implement-spec
Implement a specification (or specific phases) using coordinated subagents with unit tests, integration tests, docs, and code-review compliance. Tracks progress by updating the spec. Triggers on "implement spec", "implement phases", "build from spec", "code the spec". - 100tdd-implement
Implement a feature or fix a bug using strict TDD. Analyzes the requirement, creates tests first, implements minimal code, then refactors. Use for feature requests, bug fixes, or enhancements that need test coverage.