specflow-developlisted

Implement code from specs using a recursive orchestration model. Explores the codebase, researches best practices, plans the minimum implementation, codes it, and verifies via the test cascade: atomic tests at spec level, spec tests at domain level, journey tests at slice level. Self-similar at every scope — the same skill runs at slice, domain, and spec granularity. At each level: explore, plan, check size, either execute or delegate. Parent agents verify children via tests, not code review. Codes ALL gaps (including edge cases and missing validation) and documents them for human review — never stops for gaps. Use this skill when the user says "implement this spec", "build this slice", "code this domain", "develop from specs", or any request to generate code from an existing spec tree.
pedropacheco95/cortex · ★ 1 · Testing & QA · score 74

Install: claude install-skill pedropacheco95/cortex

# Specflow: Develop Implement code from specs. The skill is recursive — it works at any scope (vertical slice, domain, individual spec) using the same explore → plan → size-check → execute-or-delegate pattern. ## Core Principles 1. **A test that passes means the code is correct.** Parent agents verify children by running tests, not by reading their code. 2. **Write the minimum code that passes the tests.** No features beyond what's tested. No speculative abstractions. No "while I'm here" improvements. 3. **Code ALL gaps, then document them.** When the agent sees something that should be handled but isn't tested, it codes the solution AND documents the gap. The agent never stops or blocks on a gap — it always implements and continues. Severity is informational for the human's review, not a control flow mechanism. 4. **The skill is self-similar.** A slice agent, a domain agent, and a spec agent all run the same logic. The only difference is scope and which test layer verifies the result. ## Prerequisites Before this skill runs: - **Specs exist** — developer specs with rules, acceptance criteria, entity references - **Tests exist and run** — specflow-tests has been run, including Phase 0 (infrastructure). Smoke tests pass. Atomic and spec tests exist (they may be failing — the code doesn't exist yet). - **Coding conventions exist** — RULES.md and/or project-specific coding skills define HOW to write code. This skill defines WHAT to implement and