Skip to content

Skills Overview

Upfront is a set of slash skills for Claude Code. Each skill is a markdown file — no dependencies, no build step.

┌──────────────────────┐
│ /upfront:vision │
│ (strategic clarity) │
└──────────┬─────────────┘
┌────────────────┼────────────────┐
▼ ▼ ▼
┌──────────┐ ┌──────────────┐ ┌──────────┐
│ /spike │ │ /feature │ │ /spike │
│ (test │ │ (define it) │ │ then │
│ the idea)│ │ │ │ /feature │
└─────┬─────┘ └──────┬───────┘ └─────┬─────┘
│ │ │
│ ┌────────────┘ │
│ │ ◄───────────────────────────┘
│ ▼
│ ┌──────────────┐
│ │ /plan │
│ │ (break down) │
│ └──────┬───────┘
│ ▼
│ ┌──────────────┐
│ │ /build │
│ │ (TDD + review│
│ │ per phase) │
│ └──────┬───────┘
│ ▼
│ ┌──────────────┐
│ │ /retro │
│ │ (check │
│ │ results) │
│ └──────┬───────┘
│ │
│ ▼
│ next feature ──────► loop back
└──► validated? ──yes──► /feature
killed? ──────────► done

Three entry points depending on what you know:

  • You know the problem: /upfront:feature/upfront:plan/upfront:build
  • You need to test the idea first: /upfront:spike → (if validated) /upfront:feature → …
  • You have a big vision: /upfront:vision → pick a path above for each feature

After shipping, /upfront:retro checks predictions against reality, then loop back for the next feature. Occasionally run /upfront:architect to check for structural drift.

SituationSkillCeremony
Big ambition, need strategic clarity/upfront:visionRumelt’s kernel: diagnosis, policies, actions
Between increments, need to reflect/upfront:incrementStructured retro + next increment steering
Need to test an idea fast/upfront:spikeRapid prototype with debt tracking
Specific concern, risk, or tradeoff/upfront:assessInteractive problem-solving
Don’t know what to build/upfront:ideateConversation only
Need to understand a codebase/upfront:exploreProduces ARCHITECTURE.md
Improve your AI instruction files/upfront:enlightenAudits CLAUDE.md/AGENTS.md, adds stack-specific examples
Need to understand a codebase you forgot/upfront:teachWalkthrough + optional quiz
Know the problem, need to define it/upfront:feature4-phase forced thinking
Need to revise a spec/upfront:refineChallenge-based iteration
Spec ready, need implementation phases/upfront:planArchitecture deep-dive + phasing
Plan ready, need to build/upfront:buildTDD + review + red team per phase
GitHub issue or clear bug/upfront:patchInvestigate + TDD + commit
Tiny change (<50 lines)/upfront:quickJust do it with TDD
Something is broken, unclear why/upfront:debugScientific method
Structural debt, need evolution plan/upfront:architectArchitecture review + evolution plan
Evolution plan ready, need to restructure/upfront:re-architectPhase-by-phase restructuring
Feature built, need a PR/upfront:shipAuto-populated from spec
Feature shipped, need to check/upfront:retroPredictions vs reality
Check tooling is current/upfront:upgradeHealth check + fix
Not sure where to start/upfront:upSmart router
Capture a quick idea or todo/upfront:noteAppend to TODO.md
Need to stop mid-work/upfront:pauseStructured handoff
Resuming from a pause/upfront:resumeContext restoration
Change sizeSkill path
<50 lines/upfront:quick
50-300 lines/upfront:patch
300+ lines, you know what to build/upfront:feature/upfront:plan/upfront:build
300+ lines, not sure yet/upfront:spike/upfront:feature/upfront:plan/upfront:build

/upfront:patch and /upfront:quick both enforce scope gates — if a change grows beyond its boundary, the skill stops and redirects you up.