How do I install the Plan And Build skill?

Run npx skillmds@latest add jokerman89/plan-and-build in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Plan And Build safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Plan And Build?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Plan And Build free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Plan And Build?

jokerman89 (@jokerman89) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Plan And Build by jokerman89 — Agent Skill

Name: Plan And Build
Author: jokerman89

Plan And Build

Use when you already have an approved design doc and just need to plan and implement it — runs PLAN then BUILD and skips review, ship, and capture. Reach for it after DEFINE and DISCOVER are done and the remaining work is breaking the design into tasks and writing the code.

jokerman89 4e60db6 2.7 KB Updated Sep 17, 2026

File contents

You are the PLAN-AND-BUILD composite shortcut.

What this skill does

Runs PLAN + BUILD phases. Skips DEFINE (design assumed done), DISCOVER (context assumed established), REVIEW/SHIP/CAPTURE (caller invokes separately).

Equivalent to:

/li:cycle --from PLAN --to BUILD

For incremental development where operator wants to plan + execute but defer review/ship.

When to use

Design doc APPROVED, ready to break into tasks + execute
Multi-day work where operator runs PLAN+BUILD this session, REVIEW+SHIP later
Iterative dogfood — build, dogfood, fix in same iteration before formal REVIEW
Cost expectation: ~20-40k tokens, 45min - 2 hours (depends on BUILD scope)

When NOT to use

No APPROVED design doc — use /li:cycle or /li:define first
Ready to ship — use /li:cycle (full) or compose with /li:review-and-ship after
Hotfix — use /li:fix (skips PLAN's heavy ceremony)
Just plan, no build — use /li:plan standalone

Workflow

Step 1 — Pre-flight

Verify:

APPROVED design doc exists in .claude/engineering/design-archive/
Operator on feature branch (not main)
Context available for PLAN

If missing: surface, suggest /li:define first OR /li:cycle for full chain.

Step 2 — Delegate

/li:cycle --from PLAN --to BUILD --skip CAPTURE

Note: only --skip CAPTURE; SENSE still runs (always, cheap) and verifies state.

Step 3 — Post-build

After BUILD DONE, surface:

PLAN + BUILD COMPLETE

Phases done: PLAN ✓ BUILD ✓
Phases deferred: REVIEW, SHIP, CAPTURE

To finish cycle later:
  /li:resume → picks up at REVIEW
  OR
  /li:review-and-ship → composite for the rest

Artifacts:
  - plan.md (APPROVED)
  - spec.md (DRAFT, finalized in CAPTURE)
  - Code commits on current branch
  - build-log.md

Pause-points

PLAN cost-estimate gate + founder approval gate
Per-task two-stage review during BUILD
HARD-RULE hooks if the active pack's compliance mode is hard (resolve_pack_field compliance.mode; advisory by default)

Integration

Delegates to /li:cycle --from PLAN --to BUILD.

Anti-patterns

Skipping REVIEW indefinitely — fine to defer one cycle, dangerous as habit
Treating this as faster /li:cycle — it just skips review/ship/capture; total cost similar minus those phases
Running on main — same hard rule as BUILD, never on main without consent

---name: plan-and-builddescription: Use when you already have an approved design doc and just need to plan and implement it — runs PLAN then BUILD and skips review, ship, and capture. Reach for it after DEFINE and DISCOVER are done and the remaining work is breaking the design into tasks and writing the code.---You are the PLAN-AND-BUILD composite shortcut.## What this skill doesRuns PLAN + BUILD phases. Skips DEFINE (design assumed done), DISCOVER (context assumed established), REVIEW/SHIP/CAPTURE (caller invokes separately).Equivalent to:```/li:cycle --from PLAN --to BUILD```For incremental development where operator wants to plan + execute but defer review/ship.## When to use- Design doc APPROVED, ready to break into tasks + execute- Multi-day work where operator runs PLAN+BUILD this session, REVIEW+SHIP later- Iterative dogfood — build, dogfood, fix in same iteration before formal REVIEW- Cost expectation: ~20-40k tokens, 45min - 2 hours (depends on BUILD scope)## When NOT to use- No APPROVED design doc — use `/li:cycle` or `/li:define` first- Ready to ship — use `/li:cycle` (full) or compose with `/li:review-and-ship` after- Hotfix — use `/li:fix` (skips PLAN's heavy ceremony)- Just plan, no build — use `/li:plan` standalone## Workflow### Step 1 — Pre-flightVerify:- APPROVED design doc exists in .claude/engineering/design-archive/- Operator on feature branch (not main)- Context available for PLANIf missing: surface, suggest `/li:define` first OR `/li:cycle` for full chain.### Step 2 — Delegate```bash/li:cycle --from PLAN --to BUILD --skip CAPTURE```Note: only --skip CAPTURE; SENSE still runs (always, cheap) and verifies state.### Step 3 — Post-buildAfter BUILD DONE, surface:```PLAN + BUILD COMPLETEPhases done: PLAN ✓ BUILD ✓Phases deferred: REVIEW, SHIP, CAPTURETo finish cycle later: /li:resume → picks up at REVIEW OR /li:review-and-ship → composite for the restArtifacts: - plan.md (APPROVED) - spec.md (DRAFT, finalized in CAPTURE) - Code commits on current branch - build-log.md```## Pause-points- PLAN cost-estimate gate + founder approval gate- Per-task two-stage review during BUILD- HARD-RULE hooks if the active pack's compliance mode is `hard` (`resolve_pack_field compliance.mode`; advisory by default)## IntegrationDelegates to `/li:cycle --from PLAN --to BUILD`.## Anti-patterns- **Skipping REVIEW indefinitely** — fine to defer one cycle, dangerous as habit- **Treating this as faster /li:cycle** — it just skips review/ship/capture; total cost similar minus those phases- **Running on main** — same hard rule as BUILD, never on main without consent

Frequently asked questions