Structured operator for new projects, refactors, and complex implementations. Claude plans and executes. Codex reviews the plan and challenges the implementation.
Usage
/full
/full <project-description>
Behavior
When invoked:
Phase 1: Intake
-
Load or Create
1shot/Context- Check for
1shot/PROJECT.md— if missing, create from intake below - Check for
1shot/LLM-OVERVIEW.md— if missing, create from template - Read
1shot/STATE.mdif resuming
- Check for
-
Structured Discovery
- What are you building?
- What's the scope?
- What's the target architecture?
- Any constraints or preferences?
-
Document Decisions
- Write to
1shot/PROJECT.md - Note key decisions in
1shot/DECISIONS.md
- Write to
-
Update
1shot/LLM-OVERVIEW.md- Fill in or refresh: what is this, stack, key files, how to run
- Keep it current — it's the single source of truth for any LLM entering this project
Phase 2: Planning
-
Docs Check
- Identify all external libraries, APIs, and tools the project will use
- Check cache:
cat ~/github/docs-cache/docs/cache/.index.md - For anything missing → run
/doc <name> <url>before coding begins - Use cached docs as source of truth — do NOT rely on training data for syntax
-
Phase-Based Plan
- Break into milestones (not every sub-step)
- Define acceptance criteria per milestone
- Identify dependencies
- Write
1shot/ROADMAP.md
-
Skill Discovery
- Check
1shot/skills/for already-pulled project skills - For each high-level task type, ask: "Is this specialized enough that a better community skill exists?"
- Specialized domains (security, blockchain, ML, infra tools, specific APIs, parsers): search SkillsMP
./scripts/skillsmp-search.sh "<task type>" --install - General tasks (write tests, refactor, add endpoint): skip search, proceed with core skills
- If a skill is pulled, note it: "Using
1shot/skills/{name}for [task type]"
- Check
-
Create Task Queue
- Use native TaskCreate for each milestone (not every sub-step)
- Set dependencies with addBlockedBy
- Tasks track milestones, not individual file edits
-
Detect Providers
command -v codex >/dev/null 2>&1 && echo "codex: yes" || echo "codex: no" command -v gemini >/dev/null 2>&1 && echo "gemini: yes" || echo "gemini: no"Note available providers in
1shot/STATE.md. -
Codex Plan Review (adversarial pass on the plan — before any code)
- If codex available, send the plan for review:
codex exec --full-auto "You are reviewing an implementation plan before execution. Here is the plan: [ROADMAP.md content]. Flag: (1) missing steps or dependencies, (2) tasks that could be combined, (3) risks not mentioned, (4) a better ordering. Be specific. Context: [PROJECT.md summary]" - Surface Codex's feedback — adjust plan if warranted, but proceed regardless
- If codex unavailable → Claude does inline self-review, continue
- If codex available, send the plan for review:
Phase 3: Execution
-
Milestone Tracking
- Work through tasks in order
- Commit after each milestone
- Update
1shot/STATE.mdwith progress
-
Dispatch Non-Premium Tasks
- For each milestone task, classify using task-classes.md and determine category
- Follow the dispatch protocol (see
~/.claude/skills/_shared/dispatch.md):- Premium tasks (planning, review, integration) → Claude handles inline
- Implementation, test, doc tasks → dispatch to best available worker for that category
- Use
python3 -m core.dispatch.run --category <category>for parallel execution - Write manifests to
1shot/dispatch/
- Review dispatch output, validate against acceptance criteria, commit
-
Burn-Down Mode
- Complete one milestone fully before starting next
- If blocked > 2 attempts: log to
1shot/BLOCKERS.md, skip, continue
-
Context Checkpoints
- At 50% context: suggest /handoff
- At 70% context: auto-create handoff
Phase 4: Completion
-
Challenge Pass (adversarial review of full implementation)
git diff $(git merge-base HEAD main)..HEAD— full diff since full started- Follow the dispatch protocol for the review (see
_shared/dispatch.md):- Dispatch to Codex for adversarial review
- Use
codex exec --json -o /tmp/full-challenge.json
- If codex unavailable: Claude performs adversarial review inline
- New issues found → fix, then re-verify
-
Verification (MANDATORY — non-negotiable)
No verification, no completion. This is non-negotiable.
Every milestone must pass through this checklist before it can be marked completed:
- Run targeted tests — if test files exist for the changed files, run them
- Run lint/static analysis — shellcheck, prettier, ruff, or whatever the project uses
- Run type check — tsc, pyright, or equivalent
- Check acceptance criteria — verify each criterion from
1shot/PROJECT.mdor the task's description - Review diff against plan — confirm changed files match what was scoped in ROADMAP.md; flag out-of-scope changes
If any check fails:
- Do not proceed to the summary — go back and fix the issue
- Re-run the failed check(s) to confirm the fix
- Document persistent failures in
1shot/BLOCKERS.md
-
Update
1shot/LLM-OVERVIEW.md- Refresh "Current State" section to reflect what was built
-
Summary
📊 Implementation Complete ├─ Milestones: X/Y completed ├─ Files changed: Z ├─ Commits: N ├─ Codex reviews: M (issues found: P) ├─ Skills pulled: Q (in 1shot/skills/) └─ Next steps: [if any]
Provider Routing
See ~/.claude/skills/_shared/dispatch.md for the dispatch protocol.
See ~/.claude/skills/_shared/providers.md for provider detection and commands.
Full-specific routing: Claude plans and reviews. Codex and Gemini execute implementation tasks via the dispatch protocol. Research tasks route to Gemini. Full is one operator, not a PMO — don't make it behave like conduct.
1shot/ Structure
1shot/
├── LLM-OVERVIEW.md # Full project context — keep updated
├── PROJECT.md # Goals, scope, acceptance criteria
├── STATE.md # Current phase and loop state
├── ROADMAP.md # Milestones and plan
├── DECISIONS.md # Decision log
├── BLOCKERS.md # Blocked items
└── skills/ # SkillsMP-pulled project skills
└── {name}/
└── SKILL.md
Only AGENTS.md and CLAUDE.md belong at the project root. Everything else goes in 1shot/.
Decision Defaults
| Ambiguity | Default |
|---|---|
| Stack | Follow CLAUDE.md defaults |
| Multiple implementations | Simplest |
| Naming | Follow existing pattern |
| Auth | Supabase Auth (email/password + Google OAuth) |
| Database | SQLite → Supabase Postgres |
| Deploy | Vercel / oci-dev |
| SkillsMP search bar | Specialized domain → search; general task → skip |
| Codex review? | Always run if available (advisory, not a gate) |
Auto-Approved Actions
- Reading any file
- Writing to scope-matched files
- Creating/updating any file under
1shot/ - Running
./scripts/skillsmp-search.sh - Running tests and linters
- Calling Codex and Gemini CLI via bash
- Git commit (not push)
- Creating native tasks
Requires Confirmation
- Destructive operations
- Git push to shared branches
- External API calls that cost money
- Deploying to production
- Major architecture changes