Getting Started

Getting started means installing our toolchain, applying it to a new or existing repository, and running your first pieces of work through it. This page outlines the steps. If you would rather work through them with us alongside your team, engage us for a Consulting Pilot.

The steps

Install the toolchain: download it
Install dev-tool and impl-tool
Both are installed for your user through the toolchain:
```
toolchain install dev-tool
toolchain install impl-tool
```
Onboard your repository
In the root of your repository, vendor our skills. They arrive in .claude/, where Claude Code finds them:
```
toolchain vendor impl-tool:context-skills
```
Then start Claude Code there and run the onboard-repository skill. It works through the onboarding with you a step at a time, proposing each file before it writes it and changing none of your source:
```
/onboard-repository
```
Check your changes
Onboarding leaves your repository with a gate: your own formatter, linter, type checker and tests, run through one set of commands. Run both after every edit and before every commit. Every agent session is held to the same two:
```
dev gate
dev test
```
Define plan notes
A plan note is one piece of work, written down so that an agent session can act on it without the conversation that produced it. It has an id, a title and a prompt:
```
issue: EXEC-0000000
title: Add login
prompt: |-
  Add a login form to the settings page
```
The prompt says what is to change and why, and names the files and commands it concerns. Write one note for each piece of work you would review on its own. Your notes wait in a queue, in the order they are to be worked.
In Claude Code, the plan-create skill writes a note from your description and places it in the queue:
```
/plan-create <tag> <description>
```
Run plan notes with impl-tool
impl-tool takes a note and starts an agent session on it, in a worktree of its own, so your checkout stays where it was and several notes can be worked at once:
```
impl-tool issue run --issue <note>
```
The work lands in small, numbered increments on the note's own branch, each one a commit, and ends with a pull request for you to review. impl-tool's reference documents each of its commands.

Questions

Email info@solidplanssoftware.com if a step does not work as described.