1---2name: project-lifecycle3description: 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.4---56# Project Lifecycle78## Route the work9101. Choose the collaboration mode: explore an unclear problem, start a chosen direction, or implement an agreed outcome.112. Identify the project stage separately: discovery, startup preparation, MVP, growth, stabilization, or maintenance.123. Select the deliverable most useful now, such as a problem statement, blueprint, prototype, code slice, test evidence, or release plan.134. Frame substantial work with current evidence, inferred problem, acceptance, actual risk, the smallest vertical slice, and explicit non-goals.145. Keep a small low-risk task to one sentence when that is enough to verify it.1516## Design Thinking bridge1718- Empathize and define during exploration.19- Ideate while moving from exploration toward startup.20- Prototype while moving from startup toward implementation.21- Test during implementation, then route new evidence back when it changes the problem.2223## Vertical slice2425- Complete one independently verifiable loop per cycle.26- Include UI, backend, data, tests, and docs only when the outcome needs them.27- Park unrelated discoveries instead of expanding the active slice.28- Return to exploration or startup when validation changes the problem or direction.
candycong2001-ui