Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

fivetaku/pumasi

Repository files navigation

English | 한국어

pumasi

Parallel coding orchestration — Claude as PM, Codex CLI as your dev team.

Delegate the building to Codex. Keep the thinking for Claude.

Quick StartWhy pumasi?How it worksFeaturesRequirements


Quick Start

1. Add the marketplace (once)

/plugin marketplace add https://github.com/fivetaku/gptaku_plugins.git

2. Install

/plugin install pumasi

Restart Claude Code after installation.

3. Install prerequisites

# Codex CLI
npm install -g @openai/codex
# yaml dependency (one-time)
cd <plugin-dir>/skills/pumasi && npm install yaml

4. Run

/pumasi Build me a Todo app with auth, storage, and API

Or trigger naturally — pumasi auto-activates when 3+ independent modules are detected.


Why pumasi?

  • Claude does not write code — It designs interfaces, writes signatures, and sets requirements. Codex does the actual implementation. Claude tokens stay cheap.
  • N modules in parallel — Three independent modules take the same wall time as one. Five modules, same story.
  • Zero-token validation — Each task gets a bash-based gate (type-check, build, test). Gates run without consuming Claude tokens.
  • Dependency-aware rounds — Tasks with dependencies get split into rounds. Round 1 completes before Round 2 starts. No integration surprises.
  • Codex-aware instructions — Codex does not infer context. Pumasi writes absolute paths, function signatures, required imports, and hard constraints into every instruction — but never the function body.

How it works

User request
 │
 ▼
Claude (PM) — plans, decomposes, writes signatures + requirements
 │
 ├──────────────────────────────────┐
 │ │
 ▼ ▼
Codex #1 Codex #2 Codex #3
(implements) (implements) (implements)
 │ │ │
 └─────────────────┴─────────────────┘
 │
 ▼
 Gate validation (bash, 0 tokens)
 │
 ▼
 Claude reviews + integrates
 │
 ▼
 Done

7-phase workflow

Phase Who What
0. Plan Claude Analyze request, design data model, confirm scope with user
1. Decompose Claude Break into independently parallelizable subtasks
2. Configure Claude Write signatures + requirements + gates into pumasi.config.yaml
3. Execute pumasi.sh Spawn N Codex instances in parallel
4. Monitor pumasi.sh Wait for all workers to complete
5. Validate Claude Run gates (tsc, build, test), read only failing code
6. Integrate Claude + Codex Verify cross-task interfaces, re-delegate fixes to Codex

Features

Role separation

Role Claude Codex
Requirements analysis Yes No
Data model design Yes No
Function signatures Yes No
Function bodies Never Yes
Gate validation Yes (run) No
Bug fixes Delegates Implements

When to use pumasi

Task count Recommendation
1–2 tasks Claude codes directly — pumasi overhead not worth it
3–4 tasks Pumasi optional — parallel gain roughly offsets setup cost
5+ tasks Pumasi strongly recommended — parallel gain is clear

When NOT to use pumasi

  • Bug fixes or modifications to existing code (context injection becomes too heavy)
  • Single-file work (no parallel benefit)
  • Tasks where gates cannot be defined (fine-tuning UI aesthetics, etc.)

Pumasi vs /batch

Pumasi /batch
Purpose Build N independent new modules in parallel Apply the same change pattern to N existing files
Workers Codex CLI (Codex tokens) Claude agents (Claude tokens)
Isolation Shared working directory Full git worktree isolation per agent
Good for Auth + DB + API, each from scratch jest→vitest migration, CSS→Tailwind conversion

Validation gates

Step 0: Install dependencies (npm install if node_modules missing)
Step 1: Run gates — tsc --noEmit → npm run build → npm test → grep checks
Step 2: Pass = read only Codex reports. Fail = read only failing code.
Step 3: Cross-task interface check (types, import paths)

Round-based dependency handling

Round 1: Shared types / utilities (N tasks in parallel)
Round 2: Tasks that depend on Round 1 (M tasks in parallel)
Round 3: Final integration (Claude direct)

Commands

pumasi.sh start [--config path] "project context"
pumasi.sh status [JOB_DIR]
pumasi.sh status --text [JOB_DIR]
pumasi.sh wait [JOB_DIR]
pumasi.sh results [JOB_DIR]
pumasi.sh stop [JOB_DIR]
pumasi.sh clean [JOB_DIR]

Triggers

Trigger Description
/pumasi [task] Start pumasi mode with task description
/pumasi Interactive menu
"품앗이로 만들어줘" Natural language trigger
"codex 외주로" Natural language trigger
3+ independent modules detected Auto-activates

Requirements


License

MIT


Claude thinks. Codex builds. You ship.

About

Claude as PM + Codex CLI as parallel outsource developers — for large parallel coding tasks

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

Contributors

AltStyle によって変換されたページ (->オリジナル) /