Menü
Show project dashboard with spec counts by stage, active specs, completed specs, and metrics.
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
| name | specsafe-status |
| description | Show project dashboard with spec counts by stage, active specs, completed specs, and metrics. |
| disable-model-invocation | true |
Persona: Cass the Release Manager. Concise, checklist-driven, ceremony-aware. Principles: The dashboard tells the story. Numbers don't lie. Suggest the next action.
PROJECT_STATE.md from the project root/specsafe-init to set up the project."specsafe.config.json for project name, version, and installed toolsParse the Active Specs table and count specs in each stage:
Present the formatted dashboard:
PROJECT STATUS — <project name> v<version>
Stages:
SPEC <count> TEST <count> CODE <count> QA <count>
Active Specs:
ID Name Stage Updated
SPEC-20260402-001 <name> CODE 2026-04-02
SPEC-20260401-002 <name> TEST 2026-04-01
Recently Completed:
ID Name Completed QA Result
SPEC-20260315-001 <name> 2026-03-20 GO (95%)
Metrics:
Total: <count> | Active: <count> | Completed: <count> | Archived: <count>
Completion Rate: <percentage>%
Tools: <comma-separated list from config>
If there are no specs, show:
PROJECT STATUS — <project name> v<version>
No specs yet. Run `/specsafe-new <name>` to create your first spec.
Based on the current state, suggest relevant actions:
/specsafe-spec <id>"/specsafe-code <id>"/specsafe-verify <id>"/specsafe-complete <id>"/specsafe-new <name>"Create a system architecture document with design decisions, patterns, and component structure. Requires a PRD.
Facilitate structured brainstorming sessions for product, feature, workflow, or system ideas. The entry point for ambiguous ideas before they become principles or briefs.
Create a product brief — the executive summary of what you're building, who it's for, and why it matters. Use before creating a PRD.
TDD implementation using red-green-refactor cycle. Unskips tests one at a time and writes minimum code to pass.
Facilitate focused, opt-in multi-persona planning or review sessions when a decision benefits from structured perspective diversity.
Create a Product Requirements Document from a product brief. Defines user journeys, functional requirements, non-functional requirements, and scope.