Skill

aidd-init

Initializes AIDD workspace scaffolding with canonical aidd/ templates and qa.tests contract in aidd/config/gates.json. Idempotent by default; use --force to refresh managed artifacts.

Python

developer-tools

automation

npx claudepluginhub grinrus/ai_driven_dev --plugin feature-dev-aidd

Configuration

Model: inherit

Tool Access

This skill is limited to using the following tools:

ReadWriteBash(python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-init/runtime/init.py *)

Preview

Follow `feature-dev-aidd:aidd-core`.

Supporting Assets

runtime/init.py

SKILL.md

Similar Skills

feature-init

Initializes feature-workflow directory structure in a project by creating docs/features/ and docs/features/DASHBOARD.md via Python script. Run first before /feature-capture.

1 file

feature-workflow

long-task-init

167

Use when ATS doc exists (or auto-skipped) but feature-list.json not yet created - scaffold project artifacts and populate features from Design §10.2

2 files

long-task

init-orchestration

Initializes SDD projects via version detection, plugin rebuild if needed, environment verification, tech pack registration, minimal scaffolding, and git setup.

sdd

Stats

Stars5

Forks0

Last CommitApr 15, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Follow feature-dev-aidd:aidd-core.

Steps

Run python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-init/runtime/init.py.
Runtime-path safety: never call relative runtime paths; use only python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-init/runtime/init.py; if ${CLAUDE_PLUGIN_ROOT} is not set, return BLOCKED with env hint.
Default behavior is idempotent: existing workspace files stay untouched unless --force is explicitly passed.
--force is limited to refreshing managed bootstrap/config artifacts and the qa.tests contract; it is not permission to overwrite user-authored workspace docs or reports.
Verify aidd/ exists and core templates were copied (aidd/AGENTS.md, aidd/docs/shared/stage-lexicon.md).
Verify aidd/config/gates.json contains qa.tests contract fields (contract_version, profile_default, commands, defaults).
Return the output contract and next actions, explicitly stating whether the run was non-destructive or a forced refresh.

Command contracts

`python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-init/runtime/init.py`

When to run: always for canonical workspace bootstrap.
Inputs: optional --force.
Outputs: initialized aidd/ structure and synced managed bootstrap/config templates with bootstrapped qa.tests contract.
Failure mode: non-zero exit on invalid workspace, write failures, or template contract mismatch.
Next action: fix workspace path/permissions or choose the correct --force mode, then rerun the same entrypoint.

Notes

Planning stage: AIDD:ACTIONS_LOG: n/a.
Without --force, do not overwrite user-authored workspace docs or reports.
With --force, refresh only managed bootstrap/config artifacts; user-authored workspace docs or reports still stay out of scope.

Additional resources

Runtime implementation: runtime/init.py (when: init behavior or flags are unclear; why: verify exact bootstrap logic and exit conditions).