What problem does it solve? Adopting a spec-driven workflow on a legacy or already-built project normally requires hand-writing a full specification for code that already exists. This Skill scans the codebase and reverse-engineers the same .teikk/spec/ artifacts (SPEC.md, PROJECT.yaml, QUICKSTART.md, WORKFLOW.md, PROJECT-MAP.md) so the project can join the workflow at the planning phase without re-describing itself. ## Core Features & Use Cases - Evidence-based scanning: Detects platform, stack, architecture, commands, testing strategy, observability, CI, and E2E setup from build manifests and source layout across Android, iOS, Flutter, and generic projects. - Confirm-before-write gate: Presents an ASSUMPTIONS block for human veto before writing anything, and enforces an Open Questions hard gate so no unresolved unknowns remain. - Drop-in spec output: Produces artifacts identical in schema to the forward spec command, including a reconstructed Traceability Matrix mapping existing tests to acceptance criteria. - Use Case: You inherit a Kotlin/Compose Android app with no documentation. Run the mapping flow to generate a complete spec, project map, and quickstart under .teikk/spec/, then proceed directly to task planning. ## Quick Start Ask the agent to map this existing codebase and generate the .teikk/spec/ artifacts so the project can enter the planning workflow.