mcpField
P
project-init

project-init

github.com/vladm3105Development1763 installsUpdated 1d ago
Repository

About project-init

A scaffolding skill for initializing new projects for an SDD workflow. It selects a domain, creates documentation folders and indexes, and applies terminology and adaptation settings.

Key features

  1. 01Select a project domain
  2. 02Create layered documentation folders
  3. 03Apply domain terminology mappings
  4. 04Generate layer index files
  5. 05Honor adaptation settings

Use cases

  1. 01Initialize SDD documentation for a new project
  2. 02Set document terminology for a domain
  3. 03Adjust scaffolding to active layers

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill project-init

After installing, type/project-initin Claude Code to confirm it loaded.

Details

From the project README

project-init

Purpose

Scaffold a brand-new project for the SDD flow: select a domain, create the 8-layer folder structure and index files, and apply domain terminology — the one-time setup that must happen before workflow execution.

Layer: cross-cutting utility (precedes BRD).

When to Use

Use when:

  • Starting a greenfield project — no docs/ structure yet.
  • The domain has not been selected.

Do NOT use when:

  • docs/01_BRD/ etc. already exist — go straight to ../doc-flow/SKILL.md.

Behavior

Run the steps in order; create folders before any documents.

1. Domain selection (first)

Ask which domain the project targets and record the choice — it drives the terminology mappings applied in step 3:

ChoiceDomain
1 (default)Financial Services
2Software / SaaS
3Healthcare
4E-commerce
5IoT
6Other / Generic
2. Folder structure

Create the 8 artifact directories plus support folders:

mkdir -p docs/{01_BRD,02_PRD,03_EARS,04_BDD,05_ADR,06_SPEC,07_TDD,08_IPLAN}
mkdir -p docs/08_IPLAN/tmp plans
3. Domain configuration

Apply the selected domain's terminology mappings (e.g. Financial: [RESOURCE_ITEM]→Position, [USER_ROLE]→Trader; Software: [RESOURCE_ITEM]→Resource, [USER_ROLE]→Account Admin; Generic: [RESOURCE_ITEM]→Entity). Create any domain-specific subdirectories.

4. Index files
touch docs/01_BRD/BRD-00_index.md docs/02_PRD/PRD-00_index.md \
      docs/03_EARS/EARS-00_index.md docs/04_BDD/BDD-00_index.md \
      docs/05_ADR/ADR-00_index.md docs/06_SPEC/SPEC-00_index.md \
      docs/07_TDD/TDD-00_index.md docs/08_IPLAN/IPLAN-00_index.yaml

Each artifact created later must complete a Document Control section (name, version, date, owner, status, revision history).

5. Validate

Confirm all 8 directories, the index files, the domain subdirectories, and plans/ exist. If anything is missing, re-run the relevant step.

6. Hand off

Report initialization complete and direct the user to ../doc-flow/SKILL.md to begin with doc-brd. Templates are referenced from ${CLAUDE_PLUGIN_ROOT}/framework/layers/NN_<X>/; copying them into the project is optional.

Adaptation

Before scaffolding, read the project adaptation profile (.aidoc/profile.yaml). Honor active_layers: create structure for the active layers only — do not scaffold a disabled skippable layer. Ignore any unknown or out-of-surface key. Authority: ${CLAUDE_PLUGIN_ROOT}/framework/governance/ADAPTATION.md.

Related Resources

  • Next: ../doc-flow/SKILL.md (start with doc-brd)
  • Layer registry: ${CLAUDE_PLUGIN_ROOT}/framework/registry/LAYER_REGISTRY.yaml
  • Templates & READMEs: ${CLAUDE_PLUGIN_ROOT}/framework/layers/NN_<X>/
  • Diagrams: ../charts-flow/SKILL.md

Comments

Markdown supported