-
Notifications
You must be signed in to change notification settings - Fork 3
Getting Started
JRS1986 edited this page May 6, 2026
·
10 revisions
This page walks through the first useful session. The goal is not to configure every advanced backend immediately; the goal is to make one small, inspected, verified change.
git clone https://github.com/JRS1986/CodingScaffold.git
cd CodingScaffold
python3 -m venv .venv
source .venv/bin/activate
python -m pip install -e ".[dev]"On Windows PowerShell outside WSL:
.venv\Scripts\Activate.ps1coding-scaffold wizard --target ~/dev/my-project
cd ~/dev/my-projectThe wizard writes .coding-scaffold/ with project facts, provider hints, routing guidance, and
first-session documentation.
OpenCode is the recommended default adapter for the first team rollout.
curl -fsSL https://opencode.ai/install | bash
coding-scaffold adapt --target . --tool opencode
opencodeInside OpenCode:
/first-session
Expected result: the agent inspects before editing, identifies run/test commands, maps key files, and proposes one safe improvement.
Inside OpenCode:
/agentic-change
Expected result:
- explorer maps relevant files
- implementer makes a bounded change
- verification runs
- reviewer challenges the result
- you receive changed files, checks, findings, and follow-up
If the loop helped, create a reusable skill:
coding-scaffold skill --target . --adapter opencode --name "Small Safe Improvement"Then create a knowledge base to preserve decisions and useful patterns:
coding-scaffold knowledge --target . --backend obsidian