start

Detects project state from filesystem artifacts and routes to the correct Specture phase skill.

1|Updated May 1, 2026
One-click install
npx skills add https://github.com/FerEscobarDev/Specture --skill start-ferescobardev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/FerEscobarDev/Specture/tree/main/skills/start
Command: npx skills add https://github.com/FerEscobarDev/Specture --skill start-ferescobardev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When resuming work on a Specture-managed project, it is unclear which phase (setup, discovery, architecture, UX, build) the project is in. This Skill removes the guesswork by inspecting files on disk and routing to the correct phase skill automatically. ## Core Features & Use Cases - Filesystem-Based State Detection: Checks for .specture/stack.yml, docs/01-requirements/business_requirements.md, docs/04-roadmap/ROADMAP.md, and UX deliverables to determine the current phase without reading full documents. - Schema Drift Check: Runs a read-only doctor.js check --brief call to surface pending migrations or errors before routing. - Docs-Index Fallback: Detects preexisting indexed documentation tagged requirements and offers a bridge generation path instead of re-running discovery. - Use Case: You return to a project after a week and say "continuemos con el roadmap". The Skill greps the ROADMAP epic checkboxes, finds pending epics, and routes directly to the build skill. ## Quick Start Say "continue" or "sigamos" at the start of a conversation and the Skill will detect the project state and route to the correct Specture phase.

Frequently Asked Questions about start

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

FAQPage Schema
How do I resume work on a Specture project?▼

Invoke the start skill or say "continue" at the beginning of a conversation. It checks which files exist on disk, such as stack.yml and ROADMAP.md, and routes you to the correct phase skill automatically.

How does Specture detect which project phase I am in?▼

It runs an ordered routing algorithm: setup detection via .specture/stack.yml, discovery via business_requirements.md, architecture via ROADMAP.md, UX via navigation_map.md and design_system.md, then build via epic checkbox states in the roadmap.

Does the Specture router read my entire project files?▼

No. Routing uses existence checks and targeted greps only, such as the frontend.framework field or epic checkbox lines. Reading full files like stack.yml or docs-index.yml during routing is explicitly forbidden to save context.

What happens if my project has preexisting documentation but no requirements file?▼

The router greps .specture/docs-index.yml for entries tagged requirements. If found, it offers to generate a bridge file via setup-docs-bridge, run discovery from scratch, or continue without a bridge.

Why does the Specture router warn about pending migrations?▼

Before routing, it runs doctor.js check --brief to detect schema drift. Pending migrations are announced in Spanish with an option to run doctor migrate, but the warning never blocks routing.