GravionLabs/elysion / .agents/skills/implementation
implementation
VerifiedRules for code changes: every change ships with tests, dispatches to <lang>-implementation. Use for implement, write code, add feature, test requests.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.3 KB |
| references/format.md | markdown | 9.6 KB |
| references/lint.md | markdown | 1.8 KB |
| references/runner-contract.md | markdown | 2.3 KB |
| references/specs.md | markdown | 1.2 KB |
| references/test-quality.md | markdown | 1.4 KB |
| schema/config.schema.json | config | 6.3 KB |
| schema/implementer.schema.json | config | 949 B |
| scripts/Format-Changed.ps1 | script | 18.8 KB |
| templates/spec.md | markdown | 607 B |
references/specs.md
View on GitHub# Spec rules
Loaded when `governance.specMap` exists in `.agents/config.json`. `specMap` maps globs of code to the spec file that describes them; `specDir` is the folder of the specs.
## What counts as a spec change
- Public API: endpoints, routes, messages, exported contracts.
- Configuration: settings, environment variables, flags.
- Behavior visible to another service or the user.
Not a spec change: refactorings, tests, internal renames.
## Rules
- When a changed file matches a `specMap` glob and the change is a spec change, update the spec file in the same commit as the code.
- A glob matches but the spec needs no change: add `no spec change needed: <spec file> — <reason>` to `notes[]` of the implementer result (exact wording; CI looks for it and `deliver` passes it on).
- `specMode` does not change what implementation does; it only decides warn or fail in CI and `code-review`.
## New service
A new top-level folder like `apps/<name>` that no `specMap` glob matches is a new service. In the same commit:
1. create `<specDir>/<name>.md` from `templates/spec.md`
2. add the `specMap` entry `<folder>/**` → that file to `.agents/config.json`
Without the entry CI never checks the new service.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |