project-init

Included with Lifetime

$97 forever

Initialize a new (greenfield) project for the SDD flow - domain selection, folder scaffolding, and index files. Use once, before any artifact creation; then hand off to doc-flow.

Writing & Docs

What this skill does


# 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:

| Choice | Domain |
|--------|--------|
| 1 (default) | Financial Services |
| 2 | Software / SaaS |
| 3 | Healthcare |
| 4 | E-commerce |
| 5 | IoT |
| 6 | Other / Generic |

### 2. Folder structure

Create the 8 artifact directories plus support folders:

```bash
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

```bash
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`

Files: 1

Size: 3.3 KB

Complexity: 12/100

Category: Writing & Docs

Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/platforms/claude-code-plugin/skills/project-init

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts