flats-implement
/flats-implement
Implement a defined Flats repository change with development-time tests and independent adversarial code review. Use when the user explicitly limits work to implementation or when called by flats-dev-workflow; requires current design-review evidence. Unqualified implement or fix requests use flats-dev-workflow.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.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 a defined Flats repository change with development-time tests and independent adversarial code review. Use when the user explicitly limits work to implementation or when called by flats-dev-workflow; requires current design-review evidence. Unqualified implement or fix requests use flats-dev-workflow.
Original author description
Implement a defined Flats repository change with development-time tests and independent adversarial code review. Use when the user explicitly limits work to implementation or when called by flats-dev-workflow; requires current design-review evidence. Unqualified implement or fix requests use flats-dev-workflow.
How it works
- Establish readiness and implement
- Review and handoff
SKILL.md preview
--- name: flats-implement description: Implement a defined Flats repository change with development-time tests and independent adversarial code review. Use when the user explicitly limits work to implementation or when called by flats-dev-workflow; requires current design-review evidence. Unqualified implement or fix requests use flats-dev-workflow. --- # Flats implementation Read the [common development protocol](../../../docs/development-protocol.md) for review, evidence and completion rules. Enter only for explicit implementation-only scope or a coordinator call; route unqualified “implement X” requests to [flats-dev-workflow](../flats-dev-workflow/SKILL.md). ## Establish readiness and implement Read the requested change, relevant code/contracts and design record. Verify current design-review evidence, including a concise reviewed record for small changes. Missing readiness returns needs-prior-stage with the exact missing record/review and design as the next step. A standalone invocation does not silently perform design; independent invocation is not prerequisite-free. Implement within the design and any applicable worktree/ownership rules. Add or update relevant tests while developing; do not postpone them until final verification. Follow the matching [playbooks](../flats-dev-workflow/SKILL.md#playbooks). Before requesting review, run [flats-deslop](../flats-deslop/SKILL.md) on the diff and rerun the affected tests; edit prose with [flats-unslop](../flats-unslop/SKILL.md). Explain material deviations. A needed contract change returns needs-design in standalone mode without editing the contract; unresolved consequential choices return needs-input. In the full workflow the coordinator handles the return. ## Review and handoff Give an eligible different-model reviewer the original request, accepted design, complete implementation/test snapshot and actual check results. Ask them to find spec violations, regressions, failure-handling errors, resource/concurrency issues, compatibility problems and weak or incorrect tests. Review all material candidate changes, not only author-selected files. Record the review's evidence with [flats-review-evidence](../flats-review-evidence/SKILL.md). Apply the common correction/re-review cycle. Return the accepted candidate, review record, development-test results and remaining integrated verification needs. A standalone implementation ends here and does not claim the final testing stage or full workflow is complete.
Versions
The database has no other skills named flats-implement.
Database snapshot: 13.11.2026 · package version b5a4192fd08b (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
- 85flats-design
Design a Flats repository change and produce or revise its specification with independent adversarial review. Use when the user explicitly limits work to design (such as designing a feature without implementing it), or when called by flats-dev-workflow. Ordinary doc/spec edits… - 90flats-dev-workflow
Coordinate a complete Flats repository change or resume development through design, implementation and testing with independent model review. Use for feature, fix, refactor, documentation, configuration, dependency and test-change requests; explicit stage-only requests use the… - 100v1-implement-unit
Use when explicitly implementing one planned ticket through independent review and a mergeable PR. Triggers on "implement this ticket end to end" or "/v1-implement-unit". - 90doompi-development
Implement scoped code changes in an existing repository and verify them with its native checks. Use when the user asks to build, change, or fix code, not for a review-only request. - 82implement-work
Use to implement one PR-sized task. - 100codex-review
Run Codex code review with Claude's independent double-check. Use when asked \"codex review\", \"review my code with codex\", or wants Codex to review code changes. For adversarial review use /codex-adversarial.