القائمة
Build the project profile through guided conversation — the grounding document every later phase reads. Establishes the mode and, for content projects, the work-unit registry.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | Discover |
| description | Build the project profile through guided conversation — the grounding document every later phase reads. Establishes the mode and, for content projects, the work-unit registry. |
| argument-hint | [--refine] [--scan] |
A guided, conversational intake that produces .genesis/discovery/context.md — the single grounding document every later phase reads. Entry point of the pipeline; no prior approval required.
.genesis/project-state.md (the mode).genesis/constitution/index.md (if it exists)discovery-greenfield.md / discovery-brownfield.md / discovery-lowfield.md.genesis/discovery/context.md when --refineproject-state.md; extract the mode. Branch all behavior on it.--refine was not passed, ask redo-or-refine..genesis/discovery/context.md and ask the user to confirm.Project Identity · Scope & Features · Constraints · Technology Preferences · Organizational Standards · Integration Points · Quality Expectations.
Greenfield's areas, plus:
git log --oneline -50), documentation state.Conversation (7 areas): Your Domain · Information Architecture · Workflow Stages (each becomes a pipeline stage) · Quality Standards · Progressive Reveal (sequential-discovery domains only) · Reference Materials · Tools & Formats. Then teach how the pipeline maps onto the domain and define the custom stages.
Unit registry (--scan to seed from existing files): map content files to unit IDs using a naming convention (propose, confirm), ask which stage each unit has reached, and write units.json:
{
"feature": "<feature-name>",
"convention": { "prefix": "U", "digits": 3, "separator": ": ", "example": "U001: Sample Title" },
"units": [
{ "id": "U001", "title": "Chapter 1: The Beginning",
"status": "in-progress", "currentStage": "dev-edit",
"entryStage": "dev-edit", "aliases": [], "notes": "Imported from chapters/ch-01.md" }
]
}
Units with no content yet are status: pending; imported units are in-progress with currentStage/entryStage set.
.genesis/discovery/context.md — the structured profile. Brownfield appends scan results + gap analysis; lowfield appends content-type definitions, workflow descriptions, and a unit-registry summary..genesis/features/<feature>/units.json (lowfield only).Run /genesis-constitute.
- "discover"
- "tell genesis about my project"
- "profile this project"
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.