القائمة
Regress, rewind, restart, reopen, or repair a SpecForge user story through MCP.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use in this repository after completing any new functionality or functional subtask. Enforces a functional commit for the delivered change, followed by a separate version bump using the repository's versionbumper tool and its own independent commit.
SpecForge-local guardrails for workflow views, CLI portal rendering, browser shims, and runtime entrypoints. Use when modifying src-vscode, workflow renderers, portal HTML generation, CLI browser bridges, or SpecForge runtime entrypoints.
Inspect SpecForge user stories, workflow state, current phase, runtime status, lineage, and files through MCP.
Use SpecForge.AI from Codex through the compact MCP facade. Trigger for creating, inspecting, advancing, approving, regressing, or operating on SpecForge user stories.
Create or import a SpecForge user story through MCP without touching .specs files directly.
Advance or approve a SpecForge user-story phase through MCP.
| name | regress-user-story |
| description | Regress, rewind, restart, reopen, or repair a SpecForge user story through MCP. |
Use specforge_query with query: "workflow" first to identify valid targets.
Use specforge_action for state changes:
request_regression for normal regression to a previous phase.rewind_workflow for rewinding executed phase history.restart_from_source after source user-story edits.reopen_completed for completed workflows with a typed reason.repair_lineage when lineage analysis reports inconsistencies.Only pass destructive: true when the user explicitly accepts deleting later derived artifacts.