What problem does it solve? When adopting Specture in an existing project that already has a large documentation folder (docs/, wiki/, *.Docs/ with 10+ Markdown files), teams face a dilemma: duplicate their docs into Specture's structure or lose the framework's state machine benefits. This Skill bridges both worlds by indexing existing docs in place and generating lightweight reference files, without moving, renaming, or duplicating any content. ## Core Features & Use Cases - Heuristic Categorization with Approval Gate: Reads the first 30 lines of each Markdown file and proposes categories (architecture, requirements, functionalities, tech-debt, etc.) based on path and content hints, requiring explicit user approval before writing anything. - Bridge File Generation: Creates referential bridge files at docs/01-requirements/, docs/02-architecture/, and docs/03-ux-ui/ that point to the real source of truth, plus a .specture/docs-index.yml concept index. - Proposed ADR Detection: Infers implicit architectural decisions (multi-tenancy, caching, token strategy) from stack.yml and docs, drafting ADRs strictly with Status: Proposed so they never bind code reviews until a human confirms. - Use Case: A team adopting Specture on a legacy .NET project with 70 docs in SGD.Docs/ runs this Skill to index everything, generate bridges, and draft 4 candidate ADRs — all without touching the original folder. ## Quick Start Ask the AI to run the docs bridge setup to index the existing documentation folder and generate Specture bridge files without modifying the original docs.
