Cursor rule Cursor
1-analysis: Market Research.
Cursor rule Cursor
1-analysis: Market Research.
Cursor rule Cursor
2-to-3-boundary: NFR Principles.
Cursor rule Cursor
Goal. First-contact triage after npx wize-dev-kit install. Decide greenfield vs brownfield, profile, objective, and route to the right persona. Always ask who the user is so the rest of the session feels personal.
Cursor rule Cursor
Wizer (Orchestrator / Knowledge Base) — Wizer is the front door of the Wize Development Kit. He knows the project context, parses raw demand, and routes to the right specialist. He keeps the team aligned and the knowledge base current.
Cursor rule Cursor
Goal. Convene a multi-agent discussion when a decision crosses concerns.
Cursor rule Cursor
Goal. Force alignment by writing the future press release and a tight FAQ before anyone builds anything. Amazon-style. If you can't write a compelling PR, you don't have a product yet.
Cursor rule Cursor
1-analysis: Product Brief.
Cursor rule Cursor
4-implementation: Quick Dev (lifecycle shortcut).
Cursor rule Cursor
1-analysis: Refresh Project Knowledge.
Cursor rule Cursor
Goal. Surface evidence that hardens the brief and trigger map. Frame the questions Pepper actually needs answered, do focused passes (market / competitors / analytics / interviews), and write the synthesis in a way Maria Hill can quote in the PRD.
Cursor rule Cursor
Goal. Capture what worked, what didn't, what surprised, and one concrete change for next sprint. A retro that ends in a vibe is a retro that didn't ship a change.
Cursor rule Cursor
Red-team review of an artifact. Used by Hawkeye on stories/architecture and by Peggy on prose.
Cursor rule Cursor
Splits large markdown (PRD, architecture, etc.) into addressable shards under {doc-name}.shards/.
Cursor rule Cursor
Goal. Distill any intent input into a canonical, preservation-validated machine contract for downstream Wize work.
Cursor rule Cursor
4-implementation: Sprint Planning.
Cursor rule Cursor
4-implementation: Sprint Status.
Cursor rule Cursor
Goal. For one story: declare the test split, the fixtures, the mocks, the environments, and the assertion targets. This is Hawkeye's contract Shuri implements against. No story enters dev without one.
Cursor rule Cursor
Goal. Final per-story decision. PASS / CONCERNS / FAIL / WAIVED with documented rationale, score, and policy mode. This is the line: a story doesn't advance past it without a recorded gate.
Cursor rule Cursor
Goal. Verify that the epic as a whole meets Fury's NFR principles: performance, security, reliability, maintainability, accessibility, cost. Story-level gates miss NFRs that emerge only at integration; this gate catches them.
Cursor rule Cursor
Goal. A structured review of one story before its gate decision. Distinct from Shuri's wize-code-review (which audits code health). This one audits AC fulfillment, test discipline, and risk-spot coverage.
Cursor rule Cursor
Goal. Build the probability × impact matrix that prioritizes the rest of TEA's work. Areas in HIGH get deep test design; areas in LOW get smoke. Without a risk profile, every story is tested the same — wasteful, and unsafe.
Cursor rule Cursor
Goal. Map every Acceptance Criterion to one or more concrete tests in the repo. Reports honest coverage: covered, partial, missing. A story with missing rows cannot pass gate.
Cursor rule Cursor
2-to-3-boundary: Tech Vision.
Cursor rule Cursor
1-analysis: Technical Research.