From agentic-dev
Use when someone asks to initialize a new project, scaffold a project, set up the development workflow, or create project structure. Also trigger on 'start new project', 'workflow setup', 'project scaffold', or 'init from template'. Even if they just say 'set up a new project', this skill is likely what they want.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agentic-dev:init-projectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scaffolds a new project with the AI-Assisted Development Workflow: directories for all 5 phases, placeholder files (PROGRESS.md, decisions index), and a starter CLAUDE.md.
Scaffolds a new project with the AI-Assisted Development Workflow: directories for all 5 phases, placeholder files (PROGRESS.md, decisions index), and a starter CLAUDE.md.
Target is $ARGUMENTS. If not provided, ask the user. Resolve relative paths against the current working directory.
If the target has workflow/plan/, ask: full re-init or cancel.
mkdir -p "$TARGET"/{workflow/{research/{manual,final/references},spec,plan/reviews,decisions,retro},src,tests}
Create .gitkeep in empty directories.
Create workflow/plan/PROGRESS.md:
# Implementation Progress
Last updated: —
## Milestone 1: TBD
| Task | Title | Role | Status | Review | Notes |
|------|-------|------|--------|--------|-------|
## Spec Gaps Discovered
(none yet)
## Blocked Items
(none yet)
Create workflow/decisions/README.md:
# Decision Records
| ID | Title | Phase | Status |
|----|-------|-------|--------|
Create README.md with placeholder sections that phases will fill in:
# {{PROJECT_NAME}}
{{ONE_LINE_DESCRIPTION}}
## Overview
{{FILL_IN_AFTER_PHASE_1 — problem statement, background, what this project does and why}}
## Getting Started
### Prerequisites
{{FILL_IN_AFTER_PHASE_2 — runtime version, system dependencies}}
### Installation
{{FILL_IN_AFTER_PHASE_2 — package manager setup, dependency installation}}
## Usage
{{FILL_IN_AFTER_PHASE_4 — examples, CLI reference, API quickstart}}
## Architecture
{{FILL_IN_AFTER_PHASE_2 — brief architecture overview with link to workflow/spec/SPEC.md}}
## Contributing
{{FILL_IN — contribution guidelines, or link to CONTRIBUTING.md}}
## License
{{FILL_IN — e.g., MIT}}
Create CLAUDE.md with the following content:
# Project Instructions
## Project
- Name: {{PROJECT_NAME}}
- Description: {{ONE_LINE_DESCRIPTION}}
## Workflow
This project follows the AI-Assisted Software Development Workflow.
| Phase | Skill | Mode |
|-------|-------|------|
| 1. Research | `/agentic-dev:research` | Normal |
| 2. Specification | `/agentic-dev:spec` | Plan/read-only |
| 3. Task Breakdown | `/agentic-dev:plan` | Normal |
| 4. Execution | `/agentic-dev:execute` | Worktree |
| 5. Verification | `/agentic-dev:verify` | Normal |
### Key Documents
- Spec: `workflow/spec/SPEC.md`
- Plan: `workflow/plan/PLAN.md`
- Progress: `workflow/plan/PROGRESS.md`
- Decisions: `workflow/decisions/`
## Architecture
{{FILL_IN_AFTER_PHASE_2 — architecture summary, 5-10 lines}}
## Build & Test
{{FILL_IN — e.g., npm install, npm test, npm run lint}}
## Tooling Preferences
{{FILL_IN — e.g., Package manager: uv, Python version: >=3.12, Linter: ruff, Formatter: ruff format}}
## Coding Standards
{{FILL_IN_AFTER_PHASE_2 — or link to workflow/spec/SPEC.md}}
Standard entries: .DS_Store, .env, editor directories.
workflow/research/manual//agentic-dev:research{{placeholders}} in CLAUDE.md are for the human to fill in — do not resolve themGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub wilsonkichoi/agentic_development_workflow --plugin agentic-dev