ワンクリックで
project-init
Initialize a new FIRE project by detecting workspace type and setting up standards.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Initialize a new FIRE project by detecting workspace type and setting up standards.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Execute work items based on their assigned mode (autopilot, confirm, validate). Supports single-item and multi-item (batch/wide) runs.
Generate implementation walkthrough for human review after run completion. Documents decisions, changes, and verification steps.
Multi-perspective idea evaluation using Six Hats analysis, impact/feasibility scoring, and collaborative shortlisting.
Shape top ideas into actionable concept briefs using Disney Strategy — Dream, Reality, Critique.
Rapid idea generation with cross-domain diversity, anti-bias enforcement, and deep thinking.
Review code written during a run, auto-fix no-brainer issues, and suggest improvements requiring confirmation. Invoked after tests pass.
| name | project-init |
| description | Initialize a new FIRE project by detecting workspace type and setting up standards. |
| version | 1.0.0 |
Let me analyze your project to get started.
</output>
Analyze project root for existing code
workspace.type = brownfield
workspace.type = greenfield
Existing project detected. I'll analyze your codebase to infer standards.
Detect tech stack (language, framework, database)
Detect structure (monolith, monorepo)
Infer coding patterns
<monorepo_detection>
Check for monorepo indicators:
- nx.json, turbo.json, pnpm-workspace.yaml, lerna.json, rush.json
- package.json with "workspaces" field
- Cargo.toml with [workspace] section
- go.work file
- Multiple independent package/dependency manifests
- Common patterns: packages/*, apps/*, services/*, libs/*
If any indicator found → workspace.structure = "monorepo"
</monorepo_detection>
<output>
Here's what I found:
**Tech Stack**: {detected_tech}
**Structure**: {detected_structure}
**Patterns**: {detected_patterns}
Does this look accurate? [Y/n/edit]
</output>
What do you want to build? Tell me about:
- What the project does
- Target users
- Key features
Analyze description, suggest tech stack
Based on your description, I suggest:
**Language**: {suggested_language}
**Framework**: {suggested_framework}
**Database**: {suggested_database}
Accept these suggestions? [Y/n/edit]
</output>
How autonomous should FIRE be when executing work items?
**[1] Autonomous** — AI executes more freely, fewer checkpoints
(medium complexity → autopilot, high → confirm)
**[2] Balanced** — Standard checkpoints based on complexity (Recommended)
(low → autopilot, medium → confirm, high → validate)
**[3] Controlled** — More human oversight, more checkpoints
(low → confirm, medium/high → validate)
Choose [1/2/3]:
</output>
<check if="response == 1">
<set>workspace.autonomy_bias = autonomous</set>
</check>
<check if="response == 2">
<set>workspace.autonomy_bias = balanced</set>
</check>
<check if="response == 3">
<set>workspace.autonomy_bias = controlled</set>
</check>
<note>Can be changed later in .specs-fire/state.yaml</note>
Monorepo detected. Let me find and analyze the modules.
<action>Find module directories by exploring:</action>
<substep>Paths from workspace config (nx.json projects, pnpm-workspace.yaml, etc.)</substep>
<substep>Common patterns: packages/*, apps/*, services/*, libs/*, modules/*</substep>
<substep>Directories with their own dependency manifest</substep>
<action>For each discovered module, analyze (AI-driven, no hardcoded mappings):</action>
<substep>Primary language (from file extensions, config files)</substep>
<substep>Build/test commands (from CI config, package scripts, Makefile)</substep>
<substep>Linter/formatter (from config files in module)</substep>
<substep>Package manager (from lock files, manifests)</substep>
<output>
Found {{module_count}} modules:
| Module | Language | Test Command | Linter |
|--------|----------|--------------|--------|
{{#each modules}}
| {{path}} | {{language}} | {{test_cmd}} | {{linter}} |
{{/each}}
Create module-specific standards?
[c] All modules — create standards for all
[s] Select — choose which modules
[n] None — I'll create them manually later
</output>
<check if="response == c or response == s">
<action>For each selected module, create {module}/.specs-fire/standards/tech-stack.md</action>
<note>Only tech-stack.md by default — other standards inherit from root</note>
</check>
Create .specs-fire/ directory
Create .specs-fire/intents/
Create .specs-fire/runs/
Create .specs-fire/standards/
Generate .specs-fire/state.yaml (include autonomy_bias, workspace.structure)
Generate standards using templates:
constitution.md — templates/constitution.md.hbs
tech-stack.md — templates/tech-stack.md.hbs
coding-standards.md — templates/coding-standards.md.hbs
testing-standards.md — templates/testing-standards.md.hbs
system-architecture.md — templates/system-architecture.md.hbs
<check if="workspace.structure == monorepo and modules_selected">
<action>For each selected module:</action>
<substep>Create {module}/.specs-fire/standards/</substep>
<substep>Generate {module}/.specs-fire/standards/tech-stack.md with detected settings</substep>
</check>
FIRE initialized!
Structure created:
```
.specs-fire/
├── state.yaml
├── intents/
├── runs/
└── standards/
├── constitution.md # Universal policies (always inherited)
├── tech-stack.md
├── coding-standards.md
├── testing-standards.md
└── system-architecture.md
{{#if modules_created}}
Module standards created:
{{#each modules_created}}
{{path}}/.specs-fire/standards/
└── tech-stack.md
{{/each}}
{{/if}}
```
Ready to capture your first intent.
What do you want to build?
</output>
<route_to>planner-agent (intent-capture)</route_to>
<output_artifacts>
| Artifact | Location | Template |
|---|---|---|
| State | .specs-fire/state.yaml | — |
| Constitution | .specs-fire/standards/constitution.md | templates/constitution.md.hbs |
| Tech Stack | .specs-fire/standards/tech-stack.md | templates/tech-stack.md.hbs |
| Coding Standards | .specs-fire/standards/coding-standards.md | templates/coding-standards.md.hbs |
| Testing Standards | .specs-fire/standards/testing-standards.md | templates/testing-standards.md.hbs |
| System Architecture | .specs-fire/standards/system-architecture.md | templates/system-architecture.md.hbs |
| Module Tech Stack | {module}/.specs-fire/standards/tech-stack.md | AI-generated |
| </output_artifacts> |
<success_criteria> Workspace type correctly detected (greenfield/brownfield) Workspace structure correctly detected (monolith/monorepo) Tech stack identified or suggested Autonomy level selected .specs-fire/ directory structure created constitution.md generated (universal policies) Standards files generated from templates state.yaml created with correct configuration If monorepo: modules detected and analyzed If monorepo: module standards created for selected modules </success_criteria>