Plan and create specrail features and outcomes using MCP tools instead of editing .specrail files directly.
When a repository uses specrail, prefer the specrail_* MCP tools for reading and changing workflow state.
If specrail_status shows that the project is not initialized yet, start with the specrail-setup skill or call specrail_init before gathering features and outcomes.
Call specrail_feature_navigate (without arguments) whenever the user wants to see all features or needs to pick one. This tool returns an interactive panel that shows:
When a feature is selected (by passing feature_id), the navigator shows outcomes with:
specrail_status to confirm whether the project is initialized and which feature or outcome is active.specrail_feature_list, specrail_feature_show, specrail_outcome_list, specrail_outcome_show, specrail_test_list, specrail_trace) before proposing changes..specrail/* files by hand.specrail_status again to verify the new state.specrail-prepare-tests skill to register the required tests for each outcome before implementation begins.specrail-run-workflow skill to drive the implement, verify, and advance loop.specrail_feature_list, specrail_feature_show, specrail_outcome_list, specrail_outcome_show, and specrail_test_list, then ask whether to create it or correct the reference.When presenting features and outcomes to confirm, use a compact structured list:
Features to create:
• calculator — Basic arithmetic operations
Outcomes:
1. addition — Verify 2 + 2 = 4
2. subtraction — Verify 2 - 1 = 1
3. multiplication — Verify 3 × 4 = 12
After each creation, confirm with: "✓ Created feature calculator with 3 outcomes."
2 + 2 = 4, 5 + 0 = 5, and 0 + 0 = 0.2 - 2 = 0, 2 - 0 = 2, and 0 - 2 = -2.If the MCP server was not launched from the project root, pass the workspace path through the cwd argument.
This skill is the planning conversation; the specrail_* tools perform the actual create and activate actions.