A middleweight workflow for serious AI-coded features: less ceremony than BMAD, more accountability than…
🪐 Pocketto
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
**Structured AI coding workflows for Claude Code and Pi.**
From a rough idea to reviewed, shipped code — without the agent improvising.
---
Why Pocketto?
Coding agents are great at *writing* code and bad at *not skipping steps*. Pocketto adds the missing discipline:
- **Plan before code.** Specs, acceptance criteria, and TDD-structured plans come before a single line is written.
- **Delegate with contracts.** Every subagent gets a "Pocket Packet" — objective, verification, stop conditions. No packet, no spawn.
- **Gate before done.** Reviews and a hard close step keep finished work from rotting in IN_PROGRESS limbo.
15 skills across a local-first Core and an optional Enterprise adapter. Use Core for the full pipeline or standalone skills without GitHub access. If your team opts in, Enterprise consumes Core's durable lifecycle events and owns GitHub reconciliation; Core itself does not call gh. Core does not perform remote synchronization. Learning? Opt into Pocket Education and the agent becomes a repository-aware mentor — you write the code, it teaches, reviews, and guides.
Install
Pi Claude Code
Release surfaces
Version 4.2.2 is built from the explicit surfaces.json manifest. It defines exactly four role names:
| Role | Host | Contents |
|------|------|----------|
| pi/core | Pi | Local-first Core workflows and neutral lifecycle CLI. |
| pi/enterprise | Pi | Additive Enterprise adapter and references; requires pi/core. |
| claude/core | Claude Code | Local-first Core workflows and neutral lifecycle CLI. |
| claude/enterprise | Claude Code | Additive Enterprise adapter and references; requires claude/core. |
Select the role artifact for the target host and install the matching Core role first. Release builds stage an explicit manifest role with node scripts/build-surfaces.js --role --output . That directory contains only the selected role. An Enterprise stage is an overlay on the matching Core stage and does not include Core entry points such as cli/index.js. pi install npm:pocketto-pi publishes one package that contains both Core and Enterprise sources so either role can be staged from it; it is not itself a Core-only tree. Enterprise is optional and adds only its adapter-owned files; it does not bundle or copy Core skills. The manifest schema is SURFACE_MANIFEST=1. The independent protocol versions are CONTRACT=3, PIPELINE=5, LIFECYCLE_SCHEMA=2, and ADAPTER_CONTRACT=2.
Pi extensions (Pi users)
Pocket's skills call Pi extensions for their core features — **advisor** (review gates), **context7** (library docs), and **subagents** (delegation). After installing, pull them in with one command:
| Required | Unlocks |
|----------|---------|
| pi-mcp-adapter | context7 MCP — library-aware code generation |
| @gotgenes/pi-subagents | subagent delegation + parallel reviews |
| @juicesharp/rpiv-advisor | advisor — LLM-to-LLM review/escalation gates |
Recommended (install with --all): @juicesharp/rpiv-ask-user-question, @tintinweb/pi-tasks, @aliou/pi-processes.
> **New here?** Start with pocket-help — a compact router that explains what Pocket is and which skill to reach for, without loading every skill into context.
Quickstart
Run a feature through the full pipeline — each stage hands off to the next:
Or just fix something:
The 15 skills
Pipeline (chained)
Each stage invokes the next at handoff, carrying spec, plan, and acceptance criteria forward. Use these for real features and non-trivial work.
| # | Skill | When to reach for it |
|---|-------|----------------------|
| 1 | pocket-pitching | Rough idea, no clear problem yet |
| 2 | pocket-grinding | Clear problem — need a spec + acceptance criteria |
| 3 | pocket-planning | Spec ready — need an execution plan |
| 4 | pocket-structuring | Plan ready — index + task files for all plans; phase manifests when phaseCount > 1 |
| 5 | pocket-development | Plan ready — execute task-by-task via subagents, with an in-loop audit and phase-level pass |
| 6 | pocket-closing | After the phase-level pass — gate, close, summarize |
Standalone skills
Lighter, single-purpose, no pipeline. Reach for these for everyday work.
| Skill | When to reach for it |
|-------|----------------------|
| pocket-help | "What is Pocket?", which skill to use, how the flow works |
| pocket-init | Onboard an existing project: generate CLAUDE.md/AGENTS.md and optionally calibrate Education |