Skip to content

GravionLabs/elysion / .agents/skills/implementation

implementation

Verified

Rules for code changes: every change ships with tests, dispatches to <lang>-implementation. Use for implement, write code, add feature, test requests.

references/runner-contract.md

View on GitHub
# Runner contract

How `implementation` behaves as the implementer role when a runner (such as `deliver`) or a caller starts it for one PBI or Bug. Interactive use is unchanged; this file only adds the input, the rules and the result.

## Input

- the PBI or Bug issue body (scope, Technical Notes, Invariants) with its acceptance criteria
- the worktree: the working directory, already on the issue branch
- the role: `implement` (default) or `fix` (a fix round with findings); `SKILL.md` `## Lessons` passes it to `Get-Lessons.ps1 -Role`

Read the files the issue names, then follow `SKILL.md` and the `<lang>-implementation` skill from `detect-techstack`.

## Rules

- Commit the change with the issue number in the message (`<type>: <description> (#<nr>)`, last footer line `Refs #<nr>`); files added by name.
- Never call `gh`: no issue, comment, label or pull request calls. The caller owns GitHub.
- Never push. The caller pushes.
- Stay inside the worktree and the files of the issue; a criterion that cannot be met as written ends in `blocked`, not in a reinterpretation.
- Spec rules (`specs.md`): a matching `specMap` entry without a needed spec change puts `no spec change needed: <spec file> — <reason>` into `notes`; the runner passes that line on.
- Tests and format per `SKILL.md` before the commit.

## Result

Print one JSON object that validates against `schema/implementer.schema.json`, nothing else.

| Property       | Meaning                                                                        |
| -------------- | ------------------------------------------------------------------------------ |
| `status`       | `done` (committed, tests green) or `blocked` (nothing committed that is red)   |
| `commit`       | SHA of the commit; `null` when `blocked` without a commit                      |
| `filesChanged` | paths changed by the commit, relative to the worktree                          |
| `testsRun`     | the test commands run and their outcome, one string                            |
| `notes`        | decisions, deviations, follow-ups; for `blocked` the reason and what is needed |

```json
{
  "status": "done",
  "commit": "a1b2c3d",
  "filesChanged": ["src/parse.ts", "src/parse.test.ts"],
  "testsRun": "pnpm vitest run src/parse.test.ts: 6 passed",
  "notes": []
}
```
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall