/setup

Auto-generate project workflow config from existing PRD and CLAUDE.md. Zero interactive questions — all answers extracted from project data that already exists after /scaffold.

When to use

After /scaffold creates a project, before /plan. Creates docs/workflow.md so /plan and /build can work.

MCP Tools (use if available)

• project_info(name) — get project details, detected stack
• kb_search(query) — search for dev principles, manifest, stack templates
• codegraph_query(query) — check project dependencies in code graph

If MCP tools are not available, fall back to reading local files only.

Steps

1. Detect project root:
2. If $ARGUMENTS is provided, look for a project with that name in the current directory or projects_dir from ~/.solo-factory/defaults.yaml.
3. Otherwise use current working directory.
4. Verify the directory exists and has CLAUDE.md.

5. If not found, ask via AskUserQuestion.

6. Check if already initialized:

7. If docs/workflow.md exists, warn and ask whether to regenerate.

8. Read project data (parallel — all reads at once):

9. CLAUDE.md — tech stack, architecture, commands, Do/Don't
10. docs/prd.md — problem, users, solution, features, metrics, pricing
11. package.json or pyproject.toml — exact dependency versions
12. Makefile — available commands

13. Linter configs (.eslintrc*, eslint.config.*, .swiftlint.yml, ruff.toml, detekt.yml)

14. Read ecosystem sources (optional — enhances quality):

15. Detect stack name from CLAUDE.md (look for "Stack:" or the stack name in tech section).
16. If MCP kb_search available: search for stack template and dev-principles.
17. Otherwise: look for stacks/<stack>.yaml and dev-principles.md in .solo/ or plugin templates directory (if accessible).

18. If neither available: derive all info from CLAUDE.md + package manifest (sufficient).

19. Detect languages from package manifest:

20. package.json → TypeScript
21. pyproject.toml → Python
22. *.xcodeproj or Package.swift → Swift

23. build.gradle.kts → Kotlin

24. Create docs directory if needed: bash mkdir -p docs

25. Generate docs/workflow.md: Based on dev-principles (from MCP/KB or built-in defaults): ```markdown # Workflow — {ProjectName}

## TDD Policy Moderate — Tests encouraged but not blocking. Write tests for: - Business logic and validation - API route handlers - Complex algorithms Tests optional for: UI components, one-off scripts, prototypes.

## Test Framework

## Commit Strategy Conventional Commits Format: <type>(<scope>): <description> Types: feat, fix, refactor, test, docs, chore, perf, style

## Verification Checkpoints After each phase completion: 1. Run tests — all pass 2. Run linter — no errors 3. Run build — successful (if applicable) 4. Manual smoke test

## Branch Strategy - main — production-ready - feat/<track-id> — feature branches - fix/<description> — hotfixes ```

1. Update CLAUDE.md — add workflow reference to Key Documents section if not present.

2. Show summary and suggest next step: ``` Setup complete for {ProjectName}!

Created: docs/workflow.md — TDD moderate, conventional commits

Next: /plan "Your first feature" ```

Common Issues

CLAUDE.md not found

Cause: Project not scaffolded or running from wrong directory. Fix: Run /scaffold first, or ensure you're in the project root with CLAUDE.md.

workflow.md already exists

Cause: Previously set up. Fix: Skill warns and asks whether to regenerate. Existing file is preserved unless you confirm overwrite.

Wrong test framework detected

Cause: Multiple test frameworks in devDependencies. Fix: Skill picks the first found. Edit docs/workflow.md manually to specify the correct framework.