القائمة
Pipeline dashboard — current feature, position, per-group progress, approvals, pending PRs, blockers. Read-only, any time.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | Status |
| description | Pipeline dashboard — current feature, position, per-group progress, approvals, pending PRs, blockers. Read-only, any time. |
| argument-hint | [feature-name] [--all] [--json] |
The pipeline dashboard. Reads on-disk state and reports. Never writes approval records — a deterministic filesystem read, no generative step. Runs any time.
.genesis/project-state.md (active feature, mode).genesis/features/<feature>/approvals/master.json (feature-level phases).genesis/features/<feature>/approvals/group-{N}.json (group progress)micro-specs/*.md frontmatter (per-spec status)units.json (lowfield unit progress)git status / git log (uncommitted work, recent commits)gh for pending PRs (if available); a NEEDS_CLARIFICATION marker scanproject-state.md for the active feature and mode.master.json; count micro specs per group from the micro-specs/ directory.group-{N}.json for spec-level detail.units.json for unit progress.NEEDS_CLARIFICATION markers.--json). --all shows every feature.FEATURE: <name> BRANCH: ... MODE: <mode> PHASE: ...
Pipeline:
[x] Brainstorm / Design / Specify / North Star / Micro Specs
[ ] Implement — G0: 4/4, G1: 2/6 <- current
[ ] Audits — G0: A1+ A2+ A3+ A4+ A5+, G1: pending
[ ] Final (F-pass)
Progress: 6/26 micro specs implemented PRs: 2 pending Blockers: none
Approval State: | Phase | Status | Disposition | Date | Notes |
Brownfield adds scope boundaries (files in/out of scope) and regression surface. Lowfield adds a unit-progress table with per-unit stage depth (e.g. 6/8 line-edit).
- "status"
- "where am I"
- "pipeline position"
The drift check. Compare what was built against the design doc and master spec. Sets the Double Gate — A3 cannot start until A1 is at zero findings.
Mechanical FR/AC compliance. Walk every functional requirement and acceptance criterion and render a binary Pass/Fail with evidence. No judgment about quality, direction, or architecture.
Code/content quality. Dead code, hardcoded values, leftover TODOs, weak error handling, security holes, performance traps, standards violations. Enforces the Double Gate — blocks until A1 is at zero findings.
Vision-gap analysis. Compared to the perfect-world North Star, what is missing, drifting, or underbuilt — and what to add or change now to close the gap. Not a passive alignment scorecard.
Research the world. Real web research to find what the best teams do for every technology and pattern in the build, then implement superior approaches now (not later). The only lens that brings outside knowledge.
The boundary ritual — review what just landed, record an approval, journal it, and advance the phase. The ONLY step that writes approvals, and it does NO git.