Stage 3 · build

Use the Dev team pack

Install the Dev team pack, run its first task, and follow a typical session step by step.

Build-and-ship: story splitting, implementation with adversarial review, test plans, triage, pull request descriptions, a ranked technical-debt register, migrations, launch readiness, release notes, agent-policy files, and code-quality gates.

Reach for it when: You have an agreed requirement or a triaged bug and want it implemented, verified and ready to merge.

1. Install it

npx skilldrop-cli install --pack dev-team                 # Claude Code, your user folder
npx skilldrop-cli install --pack dev-team --project       # Claude Code, this repo
npx skilldrop-cli install --pack dev-team --ide cursor    # or kiro, codex, antigravity, copilot
npx skilldrop-cli install --pack dev-team --local         # this repo, hidden from git

In Claude Code you can also add the marketplace once (/plugin marketplace add sananthanarayan/skilldrop) and run /plugin install dev-team@skilldrop.

It brings core with it, so the shared skills are there too.

2. Run the first task: find out whether your current branch is safe to merge

Before you start:

• A git repository with changes on a branch
• The reviewer subagents, for the full panel: skilldrop install --panel review (the Claude plugin includes them)

Paste this into your agent:

Is this branch safe to merge? Run a pre-merge review on the current diff.

How to tell it worked: pre-merge-review runs the project's lint, typecheck and tests through its gate script, then the reviewer panel, and ends with READY or NOT READY.

If nothing happens: If the gate script cannot find your lint or test commands, tell it what they are. If the panel is skipped, install the reviewer subagents with skilldrop install --panel review.

3. A typical session

Bring:

• the epic, story or bug report
• a repo with working lint, typecheck and test commands
• who owns the merge
• user-story-splitter: Paste the epic or feature request (use bug-triage instead for a defect). You get: Independently shippable stories with Gherkin acceptance criteria and a recommended build order. You decide: Pick the one slice to build now; criteria a test cannot assert send it back to be reshaped.
• feature-implement-loop: Hand it the slice and its acceptance criteria. You get: Code and tests, reviewed for edge cases, security and craft for up to three rounds, with a status (VERIFIED, VERIFIED WITH OPEN ITEMS or BLOCKED), a criteria-to-test table and a round log.
• pre-merge-review: Ask whether the current diff is safe to merge. You get: The gate script's lint, typecheck and test result, then findings from the correctness, security and code-quality reviewers, ending in one verdict. You decide: Gate G2 is the script's exit code: READY moves on; NOT READY goes back to implementation, at most three times before BLOCKED.
• council-review: Only if the review surfaced a design disagreement, put it to the panel. You get: Independent positions, the named cruxes, and a Chair's verdict with dissent recorded. You decide: Gate G2.1: a human merges. SPLIT and RECONSIDER leave the loop rather than revising in the diff.

You end with: A shaped story, verified code and tests, a READY verdict with the review findings, and a human merge decision.

4. Run it as a loop

A loop runs the skills in order and stops at each gate for a verdict. Install and start one:

npx skilldrop-cli install --loop --pack dev-team

• build: Take an agreed requirement to merged code through a capped generate-verify-gate loop, with a mechanical gate that decides and a human who owns the merge. Say "run the build loop on this". Stages: shape → implement → verify [G2] → decide [G2.1].
• modernize: Replace or rewrite a legacy component without changing what it does: orient in the old code, plan the restructuring and the move, record the old system's behaviour before anything is rebuilt, rebuild in small steps, prove the new one gives the same results on the recordings, and cut over only when a person accepts the evidence. Say "run the modernize loop on this". Stages: survey → plan → capture → rebuild → prove [G10] → cutover [G10.1].
• release: Take merged code to live users through a planned, reversible rollout — plan the phases and the rollback, judge readiness on evidence, draft the release notes, then a human makes the go/no-go call. Say "run the release loop on this". Stages: plan → ready [G3] → announce → go [G3.1].

Next

• Every skill in the Dev team pack: what each one makes, needs and hands off to
• The pack's page, with one-click copy for every command
• Upgrade installed skills when a new version ships

Edit this page on GitHub · View source