qwize-br/wize-development-kit

13Stars on the repository
200Mods indexed here, across every type
yesterdayLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

wize-onboarding

27

qwize-br/wize-development-kit

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.

not rated 13 yesterday A 4 tokens

wize-orchestrator

28

qwize-br/wize-development-kit

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.

not rated 13 yesterday A 52 tokens

wize-prfaq

30

qwize-br/wize-development-kit

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.

not rated 13 yesterday A 6 tokens

wize-research

34

qwize-br/wize-development-kit

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.

not rated 13 yesterday A 4 tokens

wize-retrospective

35

qwize-br/wize-development-kit

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.

not rated 13 yesterday A 7 tokens

wize-shard-doc

37

qwize-br/wize-development-kit

Cursor rule Cursor

Splits large markdown (PRD, architecture, etc.) into addressable shards under {doc-name}.shards/.

not rated 13 yesterday A 6 tokens

wize-spec

38

qwize-br/wize-development-kit

Cursor rule Cursor

Goal. Distill any intent input into a canonical, preservation-validated machine contract for downstream Wize work.

not rated 13 yesterday A 4 tokens

wize-tea-design

41

qwize-br/wize-development-kit

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.

not rated 13 yesterday A 6 tokens

wize-tea-gate

42

qwize-br/wize-development-kit

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.

not rated 13 yesterday A 6 tokens

wize-tea-nfr

43

qwize-br/wize-development-kit

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.

not rated 13 yesterday A 8 tokens

wize-tea-review

44

qwize-br/wize-development-kit

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.

not rated 13 yesterday A 6 tokens

wize-tea-risk

45

qwize-br/wize-development-kit

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.

not rated 13 yesterday A 6 tokens

wize-tea-trace

46

qwize-br/wize-development-kit

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.

not rated 13 yesterday A 6 tokens

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: