メニュー
Decompose problems and check scope against Babylon's constitutional constraints. Use before planning to ensure work traces to test cases or improves falsifiability. Enforces scope control (Article VI) and prevents feature creep.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | specification-discover |
| description | Decompose problems and check scope against Babylon's constitutional constraints. Use before planning to ensure work traces to test cases or improves falsifiability. Enforces scope control (Article VI) and prevents feature creep. |
Before planning any implementation, decompose the user's intent into its structural components and verify it survives scope control. This phase answers: Should we do this at all?
Capture User Intent — Restate what the user wants in your own words. Confirm with them before proceeding.
Decompose into Components — Break the intent into:
Scope Control Check — Answer these three questions:
If any answer is NO, tell the user explicitly and ask if they want to:
Identify Affected Principles — Scan the constitution for principles this work would touch. List them explicitly. Examples:
Check for Transition State Dependencies — If any affected principle is marked [TRANSITION STATE], STOP. Do not proceed to plan. Tell the user: "This work depends on Amendment X (pending). Implementing now would produce provisional code that may need rewrite. Options: (a) wait for amendment, (b) scope around the transition state, (c) propose spec to resolve transition state."
Output Discover Artifact — Write a brief markdown file summarizing:
Save to .specify/discover/{YYYYMMDD}-{topic}.md (create directory if needed).
specification-governspecification-governspecification-governUse this skill to generate well-branded interfaces and assets for Babylon (The Fall of America), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
Maintain the Babylon project wiki following the Karpathy LLM Wiki pattern. Use when ingesting new knowledge, updating cross-references, linting for contradictions, or keeping agent documentation current with code changes.
Implement code with TDD discipline. Enforces deterministic hashes, model pinning, and Aleksandrov Test compliance. Never implements transition-state dependencies. Follows RED/GREEN/REFACTOR for every change.
Review work for constitutional compliance. Propose amendments when primitives or prohibitions are affected. Checks against amendment registry and enforces the AI Decision Procedure (IX.3). Final gate before merge.
Generate implementation plans with design artifacts. Loads plan-template.md, enforces P0/P1 constitutional principles for the target domain. Produces architecture decisions with traceability to test cases.
Write API contracts and interface specifications. Ensures all interfaces conform to dyadic morphism constraints and subsystem ownership boundaries. Produces machine-readable specs validated against the constitution.