setup

Setup Research-Plan-Implement Workflow

This skill analyzes a project's language, framework, and tooling, then adapts the reference templates into customized skills and agents in the project's .claude/ directory.

Supporting references in this skill's directory (${CLAUDE_SKILL_DIR}) — read each when you reach the step that needs it, not upfront:

• detection.md — what to read, what to extract, how to fill gaps (Steps 1-2)
• adaptation.md — how to adapt each template: what must survive, what register to write in, where to use judgment (Step 5)
• upgrade.md — upgrading an existing install: telling a user's customizations apart from stale template, and the migration paths

Before You Start

Recommend the user create a branch first, so they can review the generated files as a diff:

Tip: I recommend creating a branch before we set up the workflow — that way
you can review the generated files as a diff before merging them into your project.

  git checkout -b setup-rpi-workflow

If they're already on a feature branch, that's fine — just make sure they know setup will create files in .claude/.

Step 1: Analyze the project

Read detection.md, then inspect the project: language, framework, package manager, test/lint/format/build/typecheck commands, database tooling, issue tracker, and where workflow artifacts should live.

Present what you found, marking anything you couldn't determine.

Then check for an existing installation (see detection.md). If one exists, switch to upgrade.md instead of continuing here.

Step 2: Fill in the gaps

Ask for whatever you couldn't detect, batched into as few turns as possible — see detection.md for the batching approach. Then present the complete configuration and confirm it before generating anything.

Step 3: Ask preferences

1. Artifacts directory — where research, designs, plans, and review metadata get written. Default to .rpi/; state it rather than asking an open question, and let them name a different root if they want one. It's flat: the type is the filename's last segment (-research, -design, -plan, -review), so nothing nests. Don't offer to customize the naming.
2. Additional commands — any custom verification commands or project-specific testing notes to fold in?
3. Gitignore — recommend ignoring the artifacts root: these are working notes, not source, and keeping them out of git keeps PRs clean. One line, .rpi/. If artifacts are already tracked, offer git rm --cached -r .rpi/ to untrack without deleting.
4. Confirm — ready to generate?