development-lifecycle
/development-lifecycle
Use when doing frontend/React/TypeScript/UI work. Auto-guides phase: understand -> plan -> grill -> implement (TDD) -> /go (4->4b review->5->5b->6). One skill, full lifecycle. Alias: /work.
- Author
- redpanda-data ↗
- Repository
- ui-harness ↗
- Licence
- MIT
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when doing frontend/React/TypeScript/UI work. Auto-guides phase: understand -> plan -> grill -> implement (TDD) -> /go (4->4b review->5->5b->6). One skill, full lifecycle. Alias: /work.
Original author description
Use when doing frontend/React/TypeScript/UI work. Auto-guides phase: understand -> plan -> grill -> implement (TDD) -> /go (4->4b review->5->5b->6). One skill, full lifecycle. Alias: /work.
How it works
- Phases
- Phase Selection
SKILL.md preview
---
name: development-lifecycle
description: "Use when doing frontend/React/TypeScript/UI work. Auto-guides phase: understand -> plan -> grill -> implement (TDD) -> /go (4->4b review->5->5b->6). One skill, full lifecycle. Alias: /work."
---
# Development Lifecycle
Auto-detect phase, guide process.
## Phases
### 0. Worktree (automatic, silent if already isolated)
Feature branch? Skip. On main/master/develop? Spawn worktree before code. [ETHOS: Worktree Isolation]
scripts/mux-worktree.sh <type>/<branch-name>
Claude invoke silent when phase 1 start on default branch. User never run.
### 1. Understand
- Explore | clarify one-at-a-time | new->2-3 approaches+tradeoffs | bug->failing test->root cause
- Spawn background agents: alternatives, prior art, edge cases parallel
- Mixed patterns area? Refactor to single pattern FIRST before add features
- **GATE: no impl code until approach approved.**
### 2. Plan
- Every step: exact file paths, exact code, expected output. No placeholders.
- Bite-sized tasks (2-5 min each)
- UI work: use `/prototype` for 2-3 runnable UI variations, review with user, pick best. See [REFERENCE.md](REFERENCE.md).
- 5+ tasks -> stacked PRs (one per logical group)
- Complex plan (5+ tasks, multi-stakeholder)? Consider `/ultraplan`
- `/codex:rescue` available -> auto-dispatch second opinion
### 2b. Grill
**GATE: no impl until plan survive grilling.**
- Auto-invoke `/grill-with-docs` | grill until every branch resolved | update CONTEXT.md + ADRs inline
- Update plan with changes | get explicit user confirmation
- Skip only if: trivial bug fix AND <3 tasks AND no architectural decisions
### 3. Implement (TDD)
- RED: failing test first | GREEN: minimal code to pass
- **Test deletion guard**: verify test+assertion count not decrease after GREEN. AI may weaken tests -> reject and redo.
- REFACTOR while green | no `setTimeout` hacks | run `--detectAsyncLeaks`
### 4-6. Ship -- `/go`
Impl done -> run `/go` to ship. Handle all:
- **4. Verify** -- types + lint + tests + browser smoke
- **4b. Review / Refine** -- self-reviewer + adversarial-reviewer agents (4b->5)
- **5. Ship** -- `/simplify` -> `/commit-push-pr` -> code-reviewer agent
- **5b. Iterate** -- monitor CI -> `/resolve-pr-feedback` -> AI self-review: up to 3 rounds, early-exit on clean; human review: address ALL (hook-enforced)
- **6. Compound** -- codify lessons as `.claude/rules/`
See `/go` skill full details. See [REFERENCE.md](REFERENCE.md) phase-specific checklists.
## Phase Selection
Full flowchart [REFERENCE.md#phase-flowchart](REFERENCE.md#phase-flowchart).
| User says | Phases |
|---|---|
| "Build a new feature" | 1->2->**2b**->3->**`/go`** |
| "Fix this bug" | 1(reproduce)->3(TDD)->**`/go`** |
| "Refactor this module" | 1->2->**2b**->3->**`/go`** |
| "Write tests for X" | 3 only |
| "Ship it" / "Create a PR" | **`/go`** only |
| "Quick question" | Just answer |
| "Batch these 5 issues" | **Sandcastle** -- parallel agents |
| "Work on this overnight" | **Sandcastle** -- AFK delegation |
See [REFERENCE.md](REFERENCE.md) detailed checklists + Sandcastle integration.
Files in this package (2)
- REFERENCE.md 16 KB
- SKILL.md 3 KB
Versions
The database has no other skills named development-lifecycle.
Database snapshot: 13.11.2026 · package version a94702bd9ac7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95senior-frontend
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality. - 100frontend-mobile-development-component-scaffold
Scaffold React and React Native components with TypeScript, accessibility, styles, and tests. Use when building reusable UI components or establishing component structure. - 90typescript-rules
React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features. - 100typescript-dev
Use when implementing a TypeScript feature or fix, or when the user requests TypeScript architecture, implementation, review, or tests. - 100frontend-implement
Phase 4 (frontend tasks). Implements one PLAN.md task in React + TypeScript + Tailwind + shadcn/ui with the UI-state and edge-case checklist. Use for each unticked frontend task after the plan is approved. - 91cook
Feature implementation orchestrator. ALWAYS use this skill for ANY code change — implement, build, add feature, create, fix bug, or any task that modifies source code. This is the default route for 70% of all requests. Runs full TDD cycle: understand → plan → test → implement →…