What problem does it solve? Starting to code from vague or ambiguous requirements leads to rework, hidden assumptions, and untestable outcomes. This Skill forces a written specification — covering objective, tech stack, architecture, testing strategy, and boundaries — before any code is written, so the human and the agent share one source of truth. ## Core Features & Use Cases - Gated four-phase workflow: Specify, Plan, Tasks, Implement — each phase requires human review before advancing, with a hard Open Questions gate that blocks saving the spec while any item is unresolved. - Architecture decision gate: For new projects, presents 2-3 architecture options (e.g., MVVM + Clean, MVVM, MVI) with trade-offs and waits for explicit human confirmation instead of silently picking one. - Traceability Matrix: Maps every acceptance criterion to at least one behavioral test, making unproven criteria a hard NO-GO at ship time. - Use Case: When asked to build a new Android feature with only a rough idea, the Skill captures the verbatim request, surfaces assumptions, asks clarifying questions one at a time, and produces a reviewed SPEC.md under .teikk/spec/ before any implementation begins. ## Quick Start Ask the agent to write a specification for your new feature or project before writing any code, and answer its clarifying questions until the spec is approved.
