Specrail Setup

Initialization rules:

• Treat initialization as repository bootstrap, not as a substitute for feature and outcome planning.
• Confirm the working directory before initializing if the repository root is unclear.
• Prefer specrail_init over manually creating .specrail/* files.
• After initialization, verify the resulting state before moving on.
• If the user wants a custom workflow structure, gather that through follow-up questions after init rather than trying to encode it into init itself.
• This skill guides the setup conversation; the MCP tools perform the actual repository mutations.

User interaction guidance:

• Tell the user whether specrail was newly initialized or was already present.
• If the repository is already initialized, summarize the current state instead of re-bootstrapping it.
• If the project was launched outside the repository root, pass the workspace path through the cwd argument.

Example:

• If specrail_status shows no initialized project, run specrail_init with no_wizard: true.
• Confirm the project is now initialized with a default solution, project, and component.
• Then move into workflow planning, test planning, and activation in that order.