القائمة
Find and close holes in the master spec before the North Star — resolve ambiguity markers, run a coverage scan, ask high-impact questions, and optionally simulate usage scenarios.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | Clarify |
| description | Find and close holes in the master spec before the North Star — resolve ambiguity markers, run a coverage scan, ask high-impact questions, and optionally simulate usage scenarios. |
| argument-hint | <feature-name> [--markers-only|--scan-only|--simulate] |
A post-spec review that finds and closes gaps before the North Star. Gate: the specify phase must be accepted (else "Accept the spec first").
.genesis/project-state.md (mode).genesis/features/<feature>/spec.md (required), design.md (required)brainstorm-log.md (optional), the constitutionapprovals/master.json (verify specify accepted)dependencies.json for this feature and its peers (cross-feature coverage check)NEEDS_CLARIFICATION markers; resolve each one at a time (question → impact → suggested answer), updating the spec and removing the marker. (--markers-only stops here.)--scan-only reports and stops.)--simulate) Run 5–10 usage scenarios against the spec text — for each, trace FRs/ACs and mark PASS (spec handles it) or GAP (it doesn't). Gaps become new questions or amendments.project-state.md.Each category is mode-aware: greenfield checks completeness of new capability; brownfield checks new-vs-modified classification, preservation of existing behavior, and scope-boundary explicitness; lowfield checks pipeline-stage and artifact-schema completeness and measurable per-stage gates. Simulation likewise differs — greenfield = standard usage; brownfield = migration paths and backward compatibility; lowfield = pipeline at scale (50+ units), mid-stream entry, stage skipping.
.genesis/features/<feature>/spec.md (resolved markers, tightened FRs/ACs, documented assumptions) and a coverage summary in the skill output.Run /genesis-northstar.
- "clarify the spec"
- "find holes in the spec"
- "simulate the spec"