skills/aidd-init/SKILL.md
Initializes AIDD workspace scaffolding for the current project. Use when bootstrapping canonical `aidd/` templates and project-owned test execution contract in `aidd/config/gates.json`. Do not use when the request is to start feature ideation (`idea-new`) or to inspect existing ticket progress (`status`).
npx skillsauth add grinrus/ai_driven_dev aidd-initInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Follow feature-dev-aidd:aidd-core.
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-init/runtime/init.py.python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-init/runtime/init.py; if ${CLAUDE_PLUGIN_ROOT} is not set, return BLOCKED with env hint.--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.aidd/ exists and core templates were copied (aidd/AGENTS.md, aidd/docs/shared/stage-lexicon.md).aidd/config/gates.json contains qa.tests contract fields (contract_version, profile_default, commands, defaults).python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-init/runtime/init.py--force.aidd/ structure and synced managed bootstrap/config templates with bootstrapped qa.tests contract.--force mode, then rerun the same entrypoint.AIDD:ACTIONS_LOG: n/a.--force, do not overwrite user-authored workspace docs or reports.--force, refresh only managed bootstrap/config artifacts; user-authored workspace docs or reports still stay out of scope.tools
Derives or refines tasklist items from PRD and plan artifacts. Use when tasklist stage prepares implementation-ready work items. Do not use when the request is plan authoring in `plan-new` or loop execution in `implement`.
testing
Generates consolidated ticket status summary and key artifact pointers. Use when checking current stage state or handoff readiness. Do not use when the request is diagnostics/inventory from `aidd-observability` or flow-state mutation via `aidd-flow-state`.
testing
Collects missing spec inputs and synchronizes answers into `spec.yaml`. Use when review-spec leaves unresolved specification fields. Do not use when the request is readiness gating in `review-spec` or task derivation in `tasks-new`.
testing
Runs review-stage validation for scope changes, findings, and follow-up task derivation. Use when review stage needs verdict and handoff tasks. Do not use when the request is direct implementation execution in `implement` or QA validation in `qa`.