project-init

Initialize a FIRE project by detecting workspace type and generating standards templates.

3|1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/4tikhonov/the-minority-report --skill project-init-4tikhonov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-init
Source: https://github.com/4tikhonov/the-minority-report/tree/main/ontologies/.specsmd/fire/agents/orchestrator/skills/project-init
Command: npx skills add https://github.com/4tikhonov/the-minority-report --skill project-init-4tikhonov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize a new FIRE project by detecting workspace type and setting up standards.

Core Features & Use Cases

  • Detects workspace type (greenfield vs brownfield) and initializes the .specs-fire structure.
  • Generates universal standards templates: constitution, tech stack, coding standards, testing standards, and system architecture.
  • Supports monorepo analysis and creates module-specific standards when applicable.

Quick Start

Run the project-init skill at the root of your repository where .specs-fire is not yet present. The skill will detect the workspace type, create the .specs-fire directory, and populate initial standards and templates for immediate use.

Frequently Asked Questions about project-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I initialize a FIRE project and auto-detect workspace type?

To initialize a FIRE project, run the skill at your repository root. It auto-detects workspace type, creates a .specs-fire directory, and populates state.yaml with initial standards templates.

What templates are generated when bootstrapping FIRE project standards?

Bootstrapping FIRE standards generates templates for constitution, tech-stack, coding-standards, testing-standards, and system-architecture within the .specs-fire directory structure.

Can I use workspace detection for brownfield repositories or only greenfield projects?

Workspace detection supports both greenfield and brownfield repositories. It analyzes existing monorepo structures and applies standard generation to initialize the .specs-fire directory.

How do I set up module-specific standards in a monorepo workspace?

Monorepo analysis detects module structures during initialization and creates module-specific standards automatically when applicable, placing them inside the generated .specs-fire directory.

What's the best way to configure coding and testing standards across a new repository?

Configuring coding and testing standards is handled by generating universal templates during workspace initialization. The skill creates structured standards files inside the .specs-fire directory.

Do I need an existing .specs-fire directory to initialize FIRE project standards?

No, you do not need an existing .specs-fire directory. Run the skill at the root of your repository where .specs-fire is not yet present to generate the structure and templates.