Menü
Advance or approve a SpecForge user-story phase through MCP.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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.
Submit refinement or approval answers for a SpecForge user story through MCP.
| name | advance-user-story |
| description | Advance or approve a SpecForge user-story phase through MCP. |
Before advancing, call specforge_query with query: "current_phase" and inspect canExecute or blocking details when present.
Before calling any mutation, briefly tell the user which SpecForge phase or gate you are about to operate and what the next expected step is. If the current phase is blocked on user validation, branch creation details, or approval, do not call advance_phase and do not implement locally. Submit only the explicit user answer through the matching gate action, or ask the user for the missing input.
To run the current phase:
{
"workspaceRoot": "<absolute repo path>",
"usId": "US-123",
"action": "advance_phase",
"params": { "actor": "user" }
}
To approve the current phase:
{
"workspaceRoot": "<absolute repo path>",
"usId": "US-123",
"action": "approve_phase",
"params": {
"baseBranch": "main",
"workBranch": "feature/us-123",
"actor": "user"
}
}
Report phase, status, generated artifact path, token usage, and commit result when returned.