メニュー
Phase B of greenfield project bootstrap. Interview the operator to produce PROJECT.json + PROJECT.md + spec/NNN-*/requirements.md (EARS-only) + acceptance/*.feature scenarios. Iterates until ears-lint.py passes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Meta-skill chaining /specify → /constitute → /plan → /tasks → spec-validation → dispatch-ready. Greenfield project from idea to parallel-dev-ready in one flow. Halts with clear remediation if any phase fails the DoD gate.
Phase C of greenfield project bootstrap. Produce constitution.md (5-15 non-negotiable articles) + steering/*.md (cross-cutting agent-wide rules). Pauses for operator review before exit.
Phase D of greenfield project bootstrap. Produce design.md + data-model.md + contracts/{openapi,asyncapi,schemas/*} + adr/NNNN-*.md. Validates contracts via swagger-cli/asyncapi/ajv before exit.
Phase E of greenfield project bootstrap. Atomize design.md + contracts into tasks.json with files_owned + dependencies + acceptance_test + risk_score per task. Iterates until task-dag-validate passes.
Query code graph database for function callers, callees, dependencies, and dead code in CubeOS and MeshSat repos.
When multiple hosts alert simultaneously (burst), create a master YouTrack issue, run per-host triage, link children, analyze correlation, and escalate the master to Claude Code.
| name | specify |
| description | Phase B of greenfield project bootstrap. Interview the operator to produce PROJECT.json + PROJECT.md + spec/NNN-*/requirements.md (EARS-only) + acceptance/*.feature scenarios. Iterates until ears-lint.py passes. |
| disable-model-invocation | true |
| allowed-tools | Read, Write, Edit, AskUserQuestion, Glob, Grep, Bash |
You are a senior product/spec author. The operator just typed /specify because they want to bootstrap a new project. They have an idea but no spec yet.
Produce these artifacts in the current project directory:
PROJECT.md — one-page charter (vision, success metrics, owners) in plain EnglishPROJECT.json — machine-readable companion (per <bootstrap-pack>/templates/PROJECT.schema.json)spec/001-<slug>/requirements.md — EARS-only requirements with REQ-NNN IDsspec/001-<slug>/acceptance/*.feature — at least one Gherkin scenario per REQ-NNNEvery line in requirements.md MUST match one of the 5 patterns (case-sensitive, mind the period):
| Pattern | Template |
|---|---|
| Ubiquitous | REQ-NNN: The <system> shall <response>. |
| Event-driven | REQ-NNN: When <trigger>, the <system> shall <response>. |
| State-driven | REQ-NNN: While <precondition>, the <system> shall <response>. |
| Optional | REQ-NNN: Where <feature>, the <system> shall <response>. |
| Unwanted | REQ-NNN: If <trigger>, then the <system> shall <response>. |
After writing requirements.md, run:
<bootstrap-pack>/scripts/validate-project-spec.py . --check ears_compliance
If it fails, iterate. Don't proceed to the next skill until ears_compliance + requirement_unique_ids both pass.
Start from <bootstrap-pack>/templates/{PROJECT.json,PROJECT.md,requirements.md,gherkin.feature}.tmpl — they have the schema in comments and placeholder text. Replace placeholders with operator-elicited content.
validate-project-spec.py --check ears_compliance passesvalidate-project-spec.py --check requirement_unique_ids passesvalidate-project-spec.py --check no_weasel_words passesOperator runs /constitute to add constitution + steering rules, then /plan for design + contracts.