Quickstart
Run your first Pocketto commands in five minutes: a tour of the full pipeline for features, plus the standalone skills for smaller work.
Two ways to use Pocketto: the full pipeline for features, or standalone skills for everything smaller. This page shows both.
The pipeline, chained
Run a feature through the full pipeline. Each stage hands off to the next:
/pocketto:pocket-grinding "add dark mode toggle"
/pocketto:pocket-planning
/pocketto:pocket-development
/pocketto:pocket-closing <plan_dir>What you will experience at each step:
- Grinding asks focused questions from business, developer, and QA lenses, then writes a spec with Given/When/Then acceptance criteria under
docs/pocket/spec/<date>-<slug>/. An independent edge-case-hunter subagent reviews the scenarios. You approve the spec before anything moves on. - Planning converts the approved spec into a TDD-structured execution plan. A spec-reviewer subagent checks coverage and the CLI dry-runs the plan. You approve the plan before derived artifacts are generated. Plan approval never authorizes implementation.
- Development initializes the execution log, then executes task by task: implementer subagents write code with Pocket Packet contracts, and a read-only auditor reviews every task. When all tasks are done, a phase-level pass reviews the whole phase. The phase ends in
REVIEW. - Closing reconciles the verdicts, advances the phase, and appends a readable section to
closeout.md. It runs because you asked: a passing verdict alone is not authorization.
Pi users
On Pi, skills are triggered by name or trigger phrase rather than slash commands: for example, say "pocket-grinding" or "before we build" with your topic. The skills themselves behave identically.
Or fix one thing
/pocketto:bug-hunting "checkout total is off by one cent"
/pocketto:hotfix "bump the rate-limit window to 60s"bug-huntingenforces confirmed root cause before any fix: evidence collection, blast-radius mapping, backward tracing, then a failing-test-first resolution.hotfixenforces a brief plan plus independent subagent review before a single line of implementation: accuracy without full pipeline ceremony.
Where things land
After the tour, your repository has durable artifacts: spec, plan, task files, log.json, review verdicts, and closeout.md, all under docs/pocket/. They are the audit trail; see Execution artifacts.
Next steps
- Want the same tour with every gate explained? Your first end-to-end project.
- Running on Pi for the first time? Pi setup.
- Only exploring? Ask the agent "what is pocket":
pocket-helporients you without loading every skill.
Installation
Install Pocketto for Pi or Claude Code from one local-first Core, set up the required Pi extensions, and verify the install with doctor.
Claude Code setup
Install Pocketto as a Claude Code plugin from the marketplace, run its skills as /pocketto: commands, configure CLAUDE.md memory, and fix setup problems.