jaewhi-park
UserAn autonomous dev team in one folder of config files — six agents that plan, build, verify, review and ship. Works in Claude Code and opencode.
Categories
Indexed Skills (24)
hire
Hiring — design per-role model assignments and an operating profile from available models, budget and project character; apply after CEO approval. Right after /kickoff or /assess, when the budget changes, or when the team is too slow or expensive
ship
Ship — full verification, docs, risk label, automatic merge-policy resolution (local / manual / auto-low-risk), then PR creation or local merge
assess
Legacy assessment — inventory, risks, parity harness, rebuild strategy (ADR). Rebuild only after the harness exists
backlog
Product function — turn ideas and requests into spec-carrying backlog items and prioritize them (docs/BACKLOG.md, optionally GitHub Issues)
build
Implement an approved plan step by step (implementer → verifier loop)
claude-md
How to write and update the repository's CLAUDE.md (commands, architecture map, conventions, Definition of Done, forbidden actions) and its template. Load at kickoff, legacy assessment, when a retro adds a rule, or when CLAUDE.md is missing or its commands no longer match reality.
handoff
Wrap up a session — update the status board (docs/STATUS.md), commit WIP, list pending decisions. Use when ending a session or when repeated compaction has made the context heavy
integrate
Integrate finished branches into main one at a time — per-branch 4-lens review → merge → conflicts resolved by the implementer → verifier PASS → next (merge queue)
kickoff
New project kickoff — charter (CHARTER), stack decision (ADR), skeleton, rules file, first plan
lang
Set the team's working language — writes the "## Language" section of CLAUDE.md via script and switches responses immediately. Use when the team answers in the wrong language or you want to change it
parallel
Run several approved, independent plans concurrently — one team-builder per plan in its own isolated worktree. Integrate afterwards with /integrate
plan
Plan a piece of work — planner writes → critic reviews → CEO approval requested
policy
Show/set the merge policy — current automatic verdict (local / manual / auto-low-risk) with its reason; with an argument, record an override in the rules file
recruit
Recruit a new role — when no existing agent fits (a different permission boundary or a separate judgment is needed), propose one to the CEO together with its model and create it on approval. The lead suggests it from /plan or /retro, never mid-build
release
Release — version decision, finalized CHANGELOG, release notes, tag commands. Tag push is the CEO's
resume
Resume a session — reconcile the status board, the plan and git, then continue from the next action. First command of a new session
retro
Retrospective — feed the causes of rework, failures, CEO intervention and incidents back into rules, skills or guardrails
review
Review a diff — 2 lenses (correctness/security) or 4 depending on risk, in parallel → fix loop
roster
Team roster — table of each agent's model, permissions and role, plus how to change budget profile or individual models (read-only)
run
Default path — take an approved plan through build → review → ship. Stops only at escalation, fix-loop overflow and merge approval
charter
Procedure, question list and template for a new project charter (docs/CHARTER.md). Load at project kickoff, when starting a new product/service/tool, or whenever goals, scope or non-goals are unclear or drifting.
legacy-assessment
Checklist for assessing a legacy codebase: inventory, risk register, seam identification, rebuild-strategy comparison and the docs/ASSESSMENT.md format. Load when starting a rebuild, modernization or large refactor of an existing system, or before changing an unfamiliar codebase substantially.
parity-harness
Procedure for pinning current behaviour before a legacy rebuild with a characterization-test / golden-output harness, and the docs/PARITY.md format. Load as the first step of any replacement, rewrite or migration of legacy code, and use it for regression verdicts at every rebuild step.
agents-md
How to write and update the repository's AGENTS.md (commands, architecture map, conventions, Definition of Done, forbidden actions) and its template. Load at kickoff, legacy assessment, when a retro adds a rule, or when AGENTS.md is missing or its commands no longer match reality.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.