map-code-base

Reverse-engineers spec artifacts from an existing codebase into the .teikk/spec/ directory.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/22Teikk/22Teikk-Agent-Skills-Hub --skill map-code-base-22teikk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: map-code-base
Source: https://github.com/22Teikk/22Teikk-Agent-Skills-Hub/tree/main/core/skills/map-code-base
Command: npx skills add https://github.com/22Teikk/22Teikk-Agent-Skills-Hub --skill map-code-base-22teikk

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about map-code-base

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a spec from an existing codebase?▼

Run the mapping flow, which scans build manifests, source layout, and tests to infer platform, stack, and architecture. It confirms assumptions with you, then writes SPEC.md, PROJECT.yaml, and supporting files under .teikk/spec/.

When should I use code mapping instead of writing a new spec?▼

Use mapping when the project already exists and the code is the source of truth. For a brand-new project with no code, use the forward spec command instead, since requirements must be elicited rather than read.

Does codebase mapping support iOS and Flutter projects?▼

Yes. It detects Android from Gradle files, iOS from Package.swift, Xcode projects, or Podfiles, Flutter from pubspec.yaml, and falls back to generic detection from package manifests like package.json, go.mod, or pyproject.toml.

Will mapping overwrite my existing SPEC.md or config files?▼

No. The skill never overwrites an existing SPEC.md, QUICKSTART.md, or WORKFLOW.md, and it is read-only over the codebase. It only writes new artifacts under .teikk/spec/ after you confirm the assumptions block.

What happens if the code cannot answer a spec question?▼

Unknowns such as the true business domain or intended performance budgets go into an Open Questions section. The mapping is not considered done until every question is resolved or explicitly deferred.