# Project Lifecycle

> Route ambiguous ideas, project startup, and substantial feature work through exploration, startup, or implementation. Use when the work needs a project-stage judgment, a concrete deliverable, or a minimum vertical slice. Do not trigger for a small fix that current code already makes clear.

- Skill: `candycong2001-ui/project-lifecycle` (Agent Skill)
- Install (CLI): `npx skillmds@latest add candycong2001-ui/project-lifecycle`
- Raw SKILL.md: https://api.skillmd.com/api/skills/candycong2001-ui/project-lifecycle/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: candycong2001-ui (https://skillmd.com/u/candycong2001-ui)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/candycong2001-ui/project-lifecycle

---


# Project Lifecycle

## Route the work

1. Choose the collaboration mode: explore an unclear problem, start a chosen direction, or implement an agreed outcome.
2. Identify the project stage separately: discovery, startup preparation, MVP, growth, stabilization, or maintenance.
3. Select the deliverable most useful now, such as a problem statement, blueprint, prototype, code slice, test evidence, or release plan.
4. Frame substantial work with current evidence, inferred problem, acceptance, actual risk, the smallest vertical slice, and explicit non-goals.
5. Keep a small low-risk task to one sentence when that is enough to verify it.

## Design Thinking bridge

- Empathize and define during exploration.
- Ideate while moving from exploration toward startup.
- Prototype while moving from startup toward implementation.
- Test during implementation, then route new evidence back when it changes the problem.

## Vertical slice

- Complete one independently verifiable loop per cycle.
- Include UI, backend, data, tests, and docs only when the outcome needs them.
- Park unrelated discoveries instead of expanding the active slice.
- Return to exploration or startup when validation changes the problem or direction.