菜单
Inspect SpecForge user stories, workflow state, current phase, runtime status, lineage, and files 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.
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.
Submit refinement or approval answers for a SpecForge user story through MCP.
| name | inspect-user-story |
| description | Inspect SpecForge user stories, workflow state, current phase, runtime status, lineage, and files through MCP. |
Use specforge_query.
When the user asks to see, view, open, review, or inspect a specific user story, prefer the SpecForge workflow portal over raw file reads:
dotnet run --project src/SpecForge.Runner.Cli/SpecForge.Runner.Cli.csproj -- serve-workflow <workspaceRoot> <usId> <urlPrefix>
Use an available localhost port for <urlPrefix>, for example http://localhost:5128/.
specforge_query or direct file reads only as supporting context when the user asks for a textual summary, when the portal cannot start, or when troubleshooting.Do not treat a Markdown dump of .specs/**/us.md as sufficient for "show me the US" unless the user explicitly asks for the raw file contents.
Common calls:
{ "workspaceRoot": "<absolute repo path>", "query": "list_user_stories" }
{ "workspaceRoot": "<absolute repo path>", "query": "workflow", "usId": "US-123" }
{ "workspaceRoot": "<absolute repo path>", "query": "current_phase", "usId": "US-123" }
Prefer concise summaries: current phase, status, blocking reason, pending questions, artifact paths, and latest timeline events.