Plan and execute Test-Window-Driven Development when meaningful real-world validation is scarce, scheduled, long-running, expensive, or tied to a market, partner, field visit, hardware rig, or limited environment. Use to maximize safe, decision-relevant, replayable evidence per test window through preflight…
Universal quality coding process: plan, TDD, reviews. Use whenever code needs to be written — ad-hoc or as part of a task. Use when: "напиши код", "закодь", "реализуй", "write code", "implement" For planning tasks → tech-spec-planning skill. For specs → user-spec-planning skill.
A tool for breaking an approved technical specification into small, separate task files. A technical specification is a document describing what software should do.
Route software work through Implementation-Driven Development when product meaning or behavior is materially uncertain and a disposable implementation can safely produce evidence. Use for ambiguous product features, new integrations, LLM or agent behavior, unfamiliar APIs, UX alternatives, legacy discovery, or…