Set up a specrail project, verify the starting state, and hand off into feature, outcome, and test planning.
Use this skill when the repository does not yet have a .specrail/ project, when specrail_status shows the project is not initialized, or when the user wants to bootstrap specrail in a new workspace.
When a repository uses specrail, prefer the specrail_* MCP tools to create and inspect the initial workflow state.
Default sequence:
specrail_status to determine whether the current directory is already initialized.specrail_init again unless the user explicitly wants to refresh missing files.specrail_init with no_wizard: true and the workspace cwd. The interactive wizard requires a live terminal that MCP cannot provide — always use no_wizard: true when initializing through MCP.specrail_status again to confirm that initialization succeeded..specrail/ structure, manifest, state file, and ledger with default solution, project, and component entries.specrail-plan-features skill to gather features and outcomes.specrail-prepare-tests skill to register required tests.specrail-run-workflow skill to execute the implement, verify, and advance loop.Initialization rules:
specrail_init over manually creating .specrail/* files.User interaction guidance:
cwd argument.Example:
specrail_status shows no initialized project, run specrail_init with no_wizard: true.