solo-setup_skill

Overview

This skill auto-generates a project workflow document (docs/workflow.md) from an existing PRD and CLAUDE.md with zero interactive questions. It is designed to run after /scaffold and before /plan to wire up TDD policy, test frameworks, commit strategy, and verification checkpoints automatically. It avoids founder/init flows and project scaffolding; use /init for founder setup and /scaffold for scaffolding.

How this skill works

The skill locates the project root (argument or current directory), verifies CLAUDE.md exists, then reads CLAUDE.md, docs/prd.md, package manifests, Makefile, and linter configs in parallel. It optionally consults knowledge base templates and dev-principles if available. From detected stack, languages, and devDeps it composes a concise docs/workflow.md and updates CLAUDE.md to reference the workflow.

When to use it

• Right after running /scaffold to initialize a project
• Before running /plan so planning can assume a standard workflow
• When you need a default TDD policy, test framework, and branch/commit strategy
• When you want zero-question, data-driven workflow setup
• Not for founder setup (/init) or project scaffolding (/scaffold)

Best practices

• Run from the project root or pass the project name argument to target the correct folder
• Ensure CLAUDE.md and docs/prd.md exist and are up to date before running
• Keep package.json or pyproject.toml accurate so test framework detection is correct
• If multiple test frameworks exist, edit docs/workflow.md afterward to choose the preferred one
• Commit existing docs/workflow.md or confirm overwrite when regenerating

Example use cases

• You finished /scaffold and need a workflow file so /plan and /build can proceed
• You want an opinionated TDD policy and verification checklist derived from your CLAUDE.md
• You need an automated conventional commits and branching policy added to project docs
• You want to auto-link workflow in CLAUDE.md Key Documents for new team members
• You want a reproducible workflow created without answering prompts