Stats
Actions
Tags
From project-scaffolder
Use this skill when the user asks about project scaffolding, CLAUDE.md templates, project tracking, or how to use the project-scaffolder plugin. Triggers on: "How do I scaffold a project?", "What templates are available?", "CLAUDE.md best practices", "project tracking", "user story management".
How this skill is triggered — by the user, by Claude, or both
Slash command
/project-scaffolder:scaffolding-guidanceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scaffold a new project with Claude Code documentation, workflow commands, skills, and project tracking.
/newScaffold a new project with Claude Code documentation, workflow commands, skills, and project tracking.
/new
Prompts for target directory and project name. Creates full project structure.
/updateUpdate Claude Code files in an existing scaffolded project to the latest version.
/update
Detects current version, shows what's changed, lets you choose what to update. Preserves CLAUDE.md and project tracking files.
project/
├── CLAUDE.md # Project hub
└── .claude/
├── settings.json # Hooks for formatting, safety, workflow, commit gate
├── commands/ # 2 workflow commands
│ ├── implement.md # Full 5-phase feature workflow
│ └── review.md # Sub-agent review with auto-fix loop
├── skills/ # 3 interactive skills
│ ├── development-workflow/
│ ├── project-standards/
│ └── exploration-helpers/
└── project/ # Project tracking
├── features/ # User story specs
├── plans/ # Implementation plans
├── workflow-state.sh # Phase state machine (with review cycle)
├── high-level-user-stories.md
└── roadmap.md
When you ask to build a feature, the hooks enforce a 5-phase workflow:
Phase 0: Discovery → Research, ask questions, create story spec (MANDATORY GATE)
Phase 1: Plan → File inventory, contracts, risks → save plan → approval → context handoff (MANDATORY)
Phase 2: Implement → Build in dependency order, tests alongside code
Phase 3: Review → Sub-agent review → auto-fix → re-review loop (COMMIT BLOCKED until passed)
Phase 4: Commit → Update tracking, conventional commit, report
Mandatory gates:
git commit until review_passedPhase progression is automated via hooks and tracked by workflow-state.sh:
none → discovery_started → discovery_complete → plan_created → plan_approved → implementation_in_progress → under_review ↔ changes_requested → review_passed → complete
Hooks auto-advance phases based on file operations (story written, plan written, code edited, committed). The review cycle (under_review ↔ changes_requested) is the only allowed backward transition.
The /review command:
under_reviewchanges_requested, stores findings, auto-fixes, re-runs reviewreview_passed, unblocks commitCommits are BLOCKED by hooks during implementation_in_progress, under_review, and changes_requested.
| File | Purpose |
|---|---|
high-level-user-stories.md | Progress tracker - START HERE |
roadmap.md | Phased implementation plan |
features/us-XXX-name.md | User story specifications |
plans/us-XXX-plan.md | Implementation plans |
workflow-state.sh | Phase state machine |
us-001-feature-name.md)US-001)| Command | Purpose |
|---|---|
/implement | Full feature workflow: discovery → plan → implement → review cycle → commit |
/review | 4-track sub-agent review with automated fix loop until all blockers are resolved |
The scaffolded settings.json includes:
| Hook Event | Purpose |
|---|---|
| SessionStart | Shows branch info and current workflow phase |
| UserPromptSubmit | Suggests /implement for feature requests; detects plan approval |
| PreToolUse (Bash) | Blocks force-push, --no-verify, git reset --hard; commit gate enforces review |
| PreToolUse (Edit/Write) | Blocks editing secrets; warns on source edits before plan approval or during review |
| PostToolUse (Edit/Write) | Auto-formats code; runs tsc on TS files; advances workflow phases; tracks fixes |
| PostToolUse (Bash) | Detects git commit → marks story complete (only from review_passed) |
| Stop | Warns about uncommitted changes; shows next workflow action |
| Skill | Location | Triggers |
|---|---|---|
development-workflow | .claude/skills/ | Feature process, git, planning |
project-standards | .claude/skills/ | User stories, documentation |
exploration-helpers | .claude/skills/ | Database, codebase, types |
When scaffolding into an existing directory:
After scaffolding, ask the template-customizer agent:
"Help me customize these templates for [your-tech-stack]"
npx claudepluginhub adegbolahan/getting-started-claude --plugin project-scaffolderScaffolds full projects from PRD + stack templates: directory structure, configs, CLAUDE.md, git repo init, GitHub push. Studies existing projects via SoloGraph, uses Context7 for library versions.
Autonomously generates complete production-ready projects from descriptions: structure, code, tests, docs, config, git. Orchestrates pipeline with verification to ensure builds and tests pass.
Use this skill for "initialize project", "set up project", "scaffold project", "create CLAUDE.md", "set up rules", "create context directory", "vibe rules", "project templates", "init new project", "set up development structure", "create .rules", "create .context", "project scaffolding", "set up pre-commit hooks", or when the user wants to initialize a new project with Claude/Cursor development templates and structured documentation.