wize-dev-kit 0.15.0 → 0.16.0

package/src/method-skills/3-solutioning/wize-nfr-principles/workflow.md

@@ -1,161 +1,33 @@
 ---
-
 code: wize-nfr-principles
-description: "Use quando o PRD estiver validado e precisar definir os princípios de NFR (perf, segurança, confiabilidade, acessibilidade, custo) que guiarão a arquitetura."
 name: NFR Principles
-phase: 3-solutioning
+phase: 2-to-3-boundary
 owner: wize-agent-solution-strategist   # Nick Fury
-status: ready
+status: stub
 ---
 
 # NFR Principles
 
-**Goal.** Define non-functional non-negotiables Tony must design against and Hawkeye must verify. Hill defers to this when sizing scope. Mantis respects the a11y/perf bars in UX specs. Shuri implements with these targets in hand.
-
-Fury drives. Output lands in `.wize/planning/nfr-principles.md`.
-
-## Inputs
-
-- `.wize/planning/prd.md`
-- `.wize/planning/tech-vision.md`
-- `.wize/planning/brief.md` (compliance constraints, audience implications)
-- Overlay perf playbooks if active:
-  - `web-overlay/playbooks/web-perf-budgets.md`
-  - `app-overlay/playbooks/mobile-perf-budgets.md`
-  - `web-overlay/playbooks/wcag-aa.md`
-  - `app-overlay/playbooks/apple-hig.md`, `material-design-3.md`
-
-## Outputs
+**Goal.** Define non-functional non-negotiables Tony must design against and Hawkeye must verify.
 
+## Output
 - `.wize/planning/nfr-principles.md`
 
-## Categories (always cover these six)
-
-For each, write **non-negotiable** + **stretch** + **deferred** (with trigger). Use the playbooks as starting points; **tighten** if PRD demands, never loosen below playbook recommendations.
-
-### 1. Performance
-
-| Tier | Targets |
-|---|---|
-| Non-negotiable | LCP ≤ 2.5s mobile, INP ≤ 200ms, CLS ≤ 0.1 (web) — cold start ≤ 1.5s mid-range (app) |
-| Stretch | LCP ≤ 1.8s, INP ≤ 100ms |
-| Deferred | Server-side LCP for edge regions — revisit when audience > 30% non-NA |
-
-### 2. Security
-
-| Tier | Items |
-|---|---|
-| Non-negotiable | OWASP Top 10 covered; auth via {{vendor}}; tokens never logged; secrets via {{provider}}; RLS on every table with user_id |
-| Stretch | SOC2 type-I controls in place by {{date}} |
-| Deferred | SOC2 type-II — revisit at $1M ARR |
-
-### 3. Reliability
-
-| Tier | Targets |
-|---|---|
-| Non-negotiable | 99.9% uptime in primary region; error budget 0.1%/month; retries idempotent with deduplication key |
-| Stretch | 99.95% uptime |
-| Deferred | Multi-region active/active — revisit per tech-vision deferred |
-
-### 4. Maintainability
-
-| Tier | Items |
-|---|---|
-| Non-negotiable | Lint + format on commit; > 80% test coverage on logic modules; ADRs for every architectural decision; deps audited monthly |
-| Stretch | < 5% files over 300 LOC; cyclomatic complexity < 15 per function |
-| Deferred | Auto-doc generation — revisit when API consumers > 3 |
-
-### 5. Accessibility
-
-| Tier | Items |
-|---|---|
-| Non-negotiable | WCAG 2.2 AA on every shipped page; keyboard-complete; axe in CI |
-| Stretch | AAA on critical flows (signup, billing) |
-| Deferred | Full screen-reader manual audit every release — revisit at next compliance review |
-
-### 6. Cost
-
-| Tier | Targets |
-|---|---|
-| Non-negotiable | Total infra ≤ ${{X}}/month under {{load}}; degradation strategy documented for 10× spike |
-| Stretch | Cost-per-active-user ≤ ${{Y}} |
-| Deferred | Per-feature cost attribution — revisit when finance asks |
-
-## Steps
-
-### 1. Read the playbooks first
-
-If web/app overlays are active, the perf and a11y playbooks already hold real targets calibrated to mid-range device + 3G fast. Use them as starting point.
-
-### 2. Tighten by audience
-
-Mid-range mobile is the playbook baseline. If your PRD audience is *more* constrained (emerging markets, kiosk hardware, healthcare older devices), tighten. Don't loosen.
-
-### 3. Map every non-negotiable to a verifier
-
-Every non-negotiable must answer the question: *Who and how do we verify this on every release?*
-
-- LCP → `web-perf-budgets.md` lighthouse-ci config.
-- WCAG → axe in CI + Hawkeye review.
-- Uptime → SLO defined in `.wize/solutioning/observability.md` (Tony).
-- Error budget → tracked in {{tool}}.
-
-A non-negotiable with no verifier is a wish.
-
-### 4. Tell the story (one paragraph)
-
-Open the doc with a paragraph: *why these numbers, and what trade-offs they imply.* Future readers re-litigate non-negotiables every six months; the story saves that hour.
-
-### 5. Hand off
-
-Mark `status: aligned`. Tony reads before architecture; Hawkeye reads before risk profile.
-
-## Output template
+## Categories
+- **Performance** — targets (LCP, p95, throughput).
+- **Security** — auth model, data classes, threat surface posture.
+- **Reliability** — uptime, error budget, retry/idempotency policy.
+- **Maintainability** — coding standards, tech-debt allowance.
+- **Accessibility** — WCAG / platform guidelines minimums.
+- **Cost** — monthly envelope and degradation strategy.
 
+## Template
 ```markdown
----
-status: aligned
-owner: Nick Fury
-created: YYYY-MM-DD
----
-
-# NFR Principles — {{project_name}}
-
-## Why these numbers
-
-{{One paragraph: target audience, country mix, device class, compliance frame. Why we picked these targets specifically.}}
-
-## Performance
-| Tier | Targets | Verifier |
-|---|---|---|
-| Non-negotiable | LCP ≤ 2.5s mobile (CWV), INP ≤ 200ms, CLS ≤ 0.1 | lighthouse-ci + web-vitals beacon |
-| Stretch | LCP ≤ 1.8s | same |
-| Deferred | Multi-region LCP — trigger: EU DAU > 5k | — |
-
-## Security
-…
-
-## Reliability
-…
-
-## Maintainability
-…
-
-## Accessibility
-…
+# NFR Principles
 
-## Cost
+| Category | Non-negotiable | Stretch | Deferred |
+|---|---|---|---|
+| Performance | … | … | … |
+| Security | … | … | … |
 …
 ```
-
-## Anti-patterns Fury rejects
-
-- **Targets without numbers.** "Fast." Wrong. "p95 server response ≤ 200ms."
-- **Stretch targets that are actually goals.** If you must hit it, it's non-negotiable.
-- **No verifier.** Every non-negotiable answers *who verifies, with what tool, on what cadence*.
-- **Loosening below the playbook.** Tightening is fine. Loosening is a smell — escalate.
-- **Cost left blank.** Cost is always an NFR.
-
-## Hand-off
-
-> NFRs at `.wize/planning/nfr-principles.md`. Tony, architecture must respect items 1.A and 4.A from day one (perf and ADR discipline). Hawkeye, your gate policy can stay advisory but NFR gate per epic is mandatory. Hill, scope must keep the budget headroom for item 6.A.

package/src/method-skills/3-solutioning/wize-tech-vision/workflow.md

@@ -1,151 +1,43 @@
 ---
-
 code: wize-tech-vision
-description: "Use quando o PRD estiver validado e precisar definir o norte técnico: stack family, build-buy-borrow e non-negotiables."
 name: Tech Vision
-phase: 3-solutioning
+phase: 2-to-3-boundary
 owner: wize-agent-solution-strategist   # Nick Fury
-status: ready
+status: stub
 ---
 
 # Tech Vision
 
-**Goal.** State the technical north star in one page. Stack family, runtime envelope, build/buy/borrow calls, non-negotiables. Fury sets the **shape**, not the libraries — Tony fills in inside the frame.
-
-Output lands in `.wize/planning/tech-vision.md`. Tony reads this before drawing architecture. Hill references it when scoping. Hawkeye uses it when picking gate granularity.
-
-## Inputs
-
-- `.wize/planning/prd.md` (validated)
-- `.wize/planning/ux/ux-design/` (so the runtime envelope respects the UX)
-- `.wize/knowledge/document-project/` (brownfield only)
-- Stack catalogs (per active overlay):
-  - `src/web-overlay/stack-catalog.md`
-  - `src/app-overlay/stack-catalog.md`
-
-## Outputs
+**Goal.** State the technical north star in one page. Stack family, language, runtime envelope, build/buy/borrow calls. Not libraries — *shape*.
 
+## Output
 - `.wize/planning/tech-vision.md`
 
-## Steps
-
-### 1. Pick the stack family
-
-By order of constraint:
-
-1. **Audience reach.** Public + SEO-critical? Authenticated app? Native mobile required?
-2. **Latency budget.** Sub-1s LCP on 3G or richer-but-slower OK?
-3. **Team familiarity.** Favor what the team has shipped before unless the project truly demands new.
-4. **Backend coupling.** Separate API / fullstack monolith / BaaS?
-5. **Deploy target.** Edge / container / self-managed.
-
-Don't pick libraries here. Pick the *shape*: "Next.js-class SSR fullstack on edge" or "React Native + Expo with a Supabase backend" or "Compose Multiplatform with Kotlin services."
-
-### 2. State the runtime envelope
-
-| Dimension | Decision |
-|---|---|
-| Language(s) of record | TS, Kotlin, etc. |
-| Runtime(s) | Browser / Node / Edge / Native iOS / Native Android / JVM |
-| Persistence | Postgres / SQLite / KV / cloud-native |
-| Deploy target | Vercel / Cloudflare / Fly / EKS / EAS / etc. |
-| Edge vs origin | Edge-first / origin-first |
-
-### 3. Build / buy / borrow
-
-For each capability the PRD implies, declare:
-
-| Capability | Build | Buy | Borrow (OSS) |
-|---|---|---|---|
-| Auth | — | Clerk / Auth0 | NextAuth / Lucia |
-| Payments | — | Stripe | — |
-| Search | — | Algolia / Typesense Cloud | Meilisearch self-hosted |
-| Queues | — | SQS / Cloud Tasks | BullMQ |
-| Analytics | — | Amplitude | PostHog OSS |
-| Email | — | Resend / Postmark | — |
-| Realtime | — | Pusher / Ably | Supabase Realtime |
-
-One row per capability. Empty cells are explicit choices.
-
-### 4. Non-negotiables
-
-The 2–5 things the team will not compromise on.
-
-Examples:
-- *"All endpoint responses ≤ 200ms p95 from the user's region."*
-- *"Single source of truth for user data — no shadow stores."*
-- *"PII never leaves the EU."*
-- *"On-call burden ≤ 0.5 pages per engineer per week."*
-
-These outrank PRD goals. If they conflict, Fury escalates.
-
-### 5. Deferred (with triggers)
-
-What we won't decide yet, and what would trigger the decision. Don't list "could be revisited"; list the *signal* that forces the decision.
-
-- *"Multi-region storage: revisit when EU+US daily active users > 5k."*
-- *"WebSockets vs SSE: revisit when realtime updates < 500ms become a PRD goal."*
-
-### 6. Hand off
-
-Mark `status: aligned`. Tony reads it as the frame; he can argue specific decisions but not redraw the family without escalating.
-
-## Output template
-
+## Template
 ```markdown
----
-status: aligned
-owner: Nick Fury
-created: YYYY-MM-DD
----
-
-# Tech Vision — {{project_name}}
+# Tech Vision
 
 ## Stack family
-Next.js-class SSR fullstack on edge, with Supabase Postgres as the system of record.
+- {Web|Mobile|Hybrid}
+
+## Language(s) of record
+- …
 
 ## Runtime envelope
-| Dimension | Decision |
-|---|---|
-| Language | TypeScript end-to-end |
-| Runtime | Edge (Vercel Edge Functions) + Node (server actions) |
-| Persistence | Supabase Postgres (RLS) + PgBouncer |
-| Deploy target | Vercel for app; Supabase managed for data |
-| Edge vs origin | Edge-first for reads; origin for writes |
+- {Browser|Node|Edge|Native iOS|Native Android}
 
-## Build / buy / borrow
-| Capability | Decision |
-|---|---|
-| Auth | Buy — Supabase Auth |
-| Payments | Buy — Stripe |
-| Search | Buy — Algolia (1st year), revisit |
-| Queues | Borrow — pg_cron + outbox pattern |
-| Analytics | Borrow — PostHog OSS |
-| Email | Buy — Resend |
+## Build vs buy vs borrow
+| Capability | Decision | Why |
+|---|---|---|
+| Auth | … | … |
+| Payments | … | … |
+| Search | … | … |
+| Queues | … | … |
+| Analytics | … | … |
 
 ## Non-negotiables
-1. PII (incl. emails) stored in the user's region only.
-2. p95 server response ≤ 200ms in the user's region.
-3. Single auth identity per human (no shadow accounts).
-4. On-call rotation never exceeds 0.5 pages/eng/week.
-
-## Deferred
-- Multi-region writes: revisit when EU active users > 2k.
-- Native mobile clients: revisit when web TTI > 4s on > 20% of sessions or PRD demands offline.
+- …
 
-## Constraints that drove this
-- Brief constraint #2 (LGPD/GDPR) ruled out global-replica DBs.
-- PRD goal G1 ruled in edge-first reads.
-- Hiring tail in TypeScript ruled out Compose Multiplatform.
+## Deferred (revisit when)
+- … (trigger: …)
 ```
-
-## Anti-patterns Fury rejects
-
-- **Picking a library here.** That's Tony. Pick the *family*.
-- **Non-negotiables that are aspirations.** "Always 100% uptime." Wrong. "Error budget ≤ 0.1% in EU region."
-- **Deferred items with no trigger.** That's procrastination.
-- **A non-negotiable that contradicts a PRD constraint silently.** Surface it, escalate it, decide it.
-
-## Hand-off
-
-> Tech vision at `.wize/planning/tech-vision.md`. Tony, build the architecture inside this frame. Hill, scope the PRD against the non-negotiables (item 1 means the global launch is back on the table only after EU baseline holds). Hawkeye, pick gate granularity assuming `policy = advisory`.

package/src/method-skills/4-implementation/wize-agent-dev/persona.md

@@ -12,18 +12,6 @@ I am **Shuri**. Wakandan technologist. I implement the story Tony wrote, against
 4. **Security & perf.** I think about both at write-time, not at review-time.
 5. **Commit with AC IDs.** Every commit cites the story acceptance criteria it advances.
 
-## Before I write new code (the reuse ladder)
-
-At the "green" step, before typing a new function, I walk this ladder in order and stop at the first "yes":
-
-1. **Does this need to exist?** → no: skip it (YAGNI).
-2. **Already in this codebase?** → reuse it, don't rewrite it.
-3. **Does the stdlib do it?** → use the stdlib.
-4. **Native platform/framework feature?** → use that.
-5. **An installed dependency does it?** → use the dependency.
-6. **Is it one line?** → write the one line.
-7. **Only then** do I write the minimum new code that makes the test pass.
-
 ## Style
 
 - File paths, AC IDs, commit-message brevity.

package/src/method-skills/4-implementation/wize-code-review/workflow.md

@@ -1,66 +1,24 @@
 ---
-
 code: wize-code-review
-description: "Use quando um PR estiver aberto e precisar de revisão de código por pares focada em saúde do código."
 name: Code Review
 phase: 4-implementation
-owner: wize-agent-dev   # Shuri (peer review)
-status: ready
+owner: wize-agent-dev   # Shuri (peer Shuri — done at PR open time)
+status: stub
 ---
 
 # Code Review
 
-**Goal.** Review code changes adversarially using parallel review layers and structured triage into actionable categories.
-
-This is **Shuri's peer code review** — separate from Hawkeye's `wize-tea-review` (which audits AC fulfillment). Both run on every story PR; they are complementary.
-
-## When to run
-
-Every PR that ships code. Quick-dev PRs get a lighter review (skip architecture checks unless they touched architecture).
+**Goal.** Self/peer review focused on code health. Separate from Hawkeye's story review.
 
-## Inputs
+## What this checks
+- Naming, structure, dead code
+- Test coverage and quality (not just presence)
+- Security obvious-misses
+- Performance obvious-misses
+- Architectural drift (call Tony if found)
 
-- The diff, PR, branch, or commit range to review.
-- The spec/story file for context (optional but recommended).
-- Existing code style and project context from `.wize/knowledge/document-project/`.
+## What this does NOT check
+- AC fulfillment — that's Hawkeye's `trace` + `review` + `gate`.
 
 ## Outputs
-
-- Inline-style findings presented in the conversation.
-- Optional patch application if the user chooses to fix findings now.
-- Updated story file with a `### Review Findings` section when a spec file is provided.
-- Updated sprint status when a story key is discovered.
-
-## Workflow architecture
-
-This skill uses **step-file architecture**:
-
-- Each step is self-contained and followed exactly.
-- Sequential enforcement: complete steps in order, no skipping.
-- State tracked in frontmatter variables set at runtime.
-- Append-only building of findings.
-
-## Critical rules
-
-- **Read completely** each step file before acting.
-- **Never** load multiple step files simultaneously.
-- **Always** halt at checkpoints and wait for human input.
-- Use CWD-relative `path:line` for every code reference.
-
-## On activation
-
-1. Load `.wize/config/project.toml` and `.wize/config/user.toml`.
-2. Resolve `user_name`, `communication_language`, `document_output_language`, `implementation_artifacts`, `planning_artifacts`.
-3. Greet the user in `communication_language`.
-4. Read fully and follow `./steps/step-01-gather-context.md`.
-
-## Steps
-
-1. `step-01-gather-context.md` — identify the diff source, construct `{diff_output}`, set `{review_mode}` and `{spec_file}`.
-2. `step-02-review.md` — launch parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor).
-3. `step-03-triage.md` — normalize, deduplicate, and classify findings into `decision_needed`, `patch`, `defer`, `dismiss`.
-4. `step-04-present.md` — present findings, resolve decisions, apply patches, update story status.
-
-## Hand-off
-
-> Code review complete for `{story_key or change}`. `{decision_needed}` decision(s), `{patch}` patch(es), `{defer}` deferred, `{dismissed}` dismissed as noise. Next: re-run review or continue to `wize-tea-review` (Hawkeye).
+- Inline comments / suggestions on the diff.

package/src/method-skills/4-implementation/wize-create-story/workflow.md

@@ -1,171 +1,27 @@
 ---
-
 code: wize-create-story
-description: "Use quando um epic estiver definido e precisar criar uma story individual com acceptance criteria detalhados."
 name: Create Story
 phase: 4-implementation
 owner: wize-agent-architect   # Tony writes; Shuri may refine
-status: ready
+status: stub
 ---
 
 # Create Story
 
-**Goal.** Author one Pull-Request-sized story with crisp acceptance criteria, named touch-points, and a contract for Hawkeye's `tea-design.md`. This is the single most-edited artifact in the lifecycle; make it useful.
-
-Tony drives. Shuri reads and proposes refinements before pulling the story.
-
-> **No estimates.** Never attach a time or effort estimate (hours, days, story points, S/M/L/XL) to a story — at any step. AI development speed has made them noise that only burns time and tokens. The only sizing question is binary: **does it fit one PR?** If not, slice it. Nothing else.
-
-## When to use
-
-- New story splits from an epic (most common — done in `wize-create-epics-and-stories`).
-- A story that comes in mid-sprint and needs a quick scaffold.
-- A `tea-gate` waived rationale created a follow-up story.
+**Goal.** Author one Pull-Request-sized story unit with crisp acceptance criteria.
 
 ## Inputs
-
-Read central docs first, expand by dependency; don't pad with unrelated files:
-
-- `AGENTS.md` + `.wize/config/project.toml` — profiles, languages, conventions.
 - `.wize/solutioning/architecture.md`
 - `.wize/solutioning/epics/{epic}.md`
-- `.wize/planning/prd.md` (the AC list)
-- `.wize/knowledge/document-project/` (brownfield baseline, if present)
-- (optional) `.wize/planning/ux/ux-design/{screen}.md`
-
-## Output
+- (optional) UX screen reference
 
+## Outputs
 - `.wize/solutioning/stories/{epic}/{story-id}.md`
 
-## Steps
-
-### 1. Name it by outcome
-
-Verb-led, user-visible. *"Onboarding: invite first teammate"* not *"Build invite form."*
-
-### 2. Frontmatter
-
-```yaml
----
-story_id: E01-S03
-epic: 01-onboarding
-status: ready-for-dev
-priority: 2          # 1=now, 2=next, 3=later
-linked_screens: [onboarding-step-1, invite-modal]
-linked_acs: [AC-02-1, AC-02-2]
----
-```
-
-### 3. Context (3–5 lines)
-
-What place this story occupies in the user journey, why it matters here, what it depends on.
-
-### 4. ACs (lifted from PRD; not reworded)
-
-Don't reword PRD ACs in a story — copy them verbatim. If they're not crisp enough, fix in the PRD first.
-
-### 5. Out of scope
-
-Explicit. Other ACs the user might think this story touches, with a one-line reason it's not here.
-
-### 6. Sources of truth
-
-List the exact docs Shuri must read before coding: `AGENTS.md`, `project.toml`, `document-project/*`, the parent epic, `architecture.md`, the linked screen, the TEA test contract, and the related code + tests already on this path.
-
-### 7. Restrictions
-
-Beyond out-of-scope: name **protected behaviors** (what must not change), **compatibility** constraints (keys, contracts, migrations), and **security** constraints (boundary validation, authz). No silent scope creep — log recommended extras separately.
-
-### 8. Validation contract
-
-Declare the **AC → test** map and the **required checks** (unit / integration / e2e, lint, format, type-check, build, security when applicable) plus which UI states (loading / empty / error) must be asserted. Hawkeye writes the real `tea-design.md`, but this is the binding shape it fills.
-
-### 9. Notes for Shuri
-
-- Touch points: files Shuri will likely edit.
-- Reuse: components from `design-system` already named.
-- `testid` map: names Hawkeye expects.
-- Edge cases worth flagging (only ones not derivable from ACs).
-
-### 10. Notes for Hawkeye
-
-A one-paragraph hint: suggested split, fixtures, mocks, environment. Hawkeye writes the real `tea-design.md` but reads this hint.
-
-## INVEST rules
-
-Every story passes:
-
-- **I**ndependent.
-- **N**egotiable.
-- **V**aluable.
-- **S**mall (≤ 1 PR) — the *only* sizing test; if it doesn't fit one PR, slice.
-- **T**estable.
-
-(INVEST's "Estimable" is dropped on purpose — see **No estimates** above. We don't size in time or points.)
-
-If any letter fails, fix before queueing.
-
-## Full story template
-
-```markdown
----
-story_id: E01-S03
-epic: 01-onboarding
-status: ready-for-dev
-priority: 2
-linked_screens: [onboarding-step-1, invite-modal]
-linked_acs: [AC-02-1, AC-02-2]
----
-
-# Story: Onboarding step 1 — invite first teammate
-
-## Context
-After sign-up the admin lands on `/onboarding`. This story implements the first
-moment-of-truth from scenario S1: inviting the first teammate.
-
-## Sources of truth (Shuri reads before coding)
-- `AGENTS.md` + `.wize/config/project.toml` · `.wize/knowledge/document-project/*`.
-- `prd.md` (AC source) · `architecture.md` · `ux-design/onboarding-step-1.md` · parent epic `01-onboarding.md`.
-- The TEA test contract for this story · related code + tests already on this path.
-
-## Acceptance criteria
-- **AC-02-1:** Given a new admin on `/onboarding`, When they enter a valid email and click "Send invite", Then a `teammate_invited` event fires and the screen advances to "Invite sent" within 1s.
-- **AC-02-2:** Given an invalid email, When the user blurs the field, Then error text appears (200ms) identifying which rule failed.
-
-## Restrictions
-- **Out of scope:** bulk invite (multiple emails) → E01-S07; custom invite message → E02-S03; "Skip for now" button — not a moment-of-truth path; out.
-- **Protected behaviors:** existing sign-up + session flow must not change.
-- **Compatibility:** `(team_id, email)` composite idempotency key — don't break existing invite rows.
-- **Security:** validate email at the server boundary; auth context required on `inviteTeammate`.
-
-## Notes for Shuri (Dev)
-- Touch points: `app/(onboarding)/invite/page.tsx`, `lib/email/send-invite.ts`, new server action `inviteTeammate`.
-- Reuse: `Button` (primary), `Input`, `Banner` (success/error) from design-system.
-- testid: `invite-form`, `invite-email`, `invite-cta`, `invite-sent-banner`.
-
-## Validation contract
-- **AC → test:** AC-02-1 → E2E happy path (Playwright @chromium @ios) + unit `validateInviteEmail`; AC-02-2 → unit invalid-email rules + component error-state.
-- **Required checks:** the unit/integration/E2E split Hawkeye declares below, plus lint, format, type-check, build. Authz asserted on the server action.
-- **States:** loading, empty, error rendered and asserted.
-
-## Notes for Hawkeye (TEA)
-Suggested split: 4 unit, 1 integration, 1 E2E.
-- Unit: validateInviteEmail, mailer payload, server action error mapping, retry policy.
-- Integration: server action calls mailer with right args (MSW on Resend).
-- E2E: happy path on Playwright @chromium @ios.
-- Risk: R-1 (mailer) — extra E2E asserts banner within 1s of click.
-
-## Done means
-Every AC has a passing test (mapped above), gate PASS/CONCERNS, story `status: ready-for-review`, knowledge axes updated if touched.
-```
-
-## Anti-patterns Tony rejects
-
-- **ACs reworded from PRD.** Source-of-truth drift.
-- **Stories with no touch points.** Shuri spends an hour finding the files.
-- **No notes for Hawkeye.** TEA designs in the dark.
-- **Stories named by feature** ("Add invite button") — name by **outcome**.
-
-## Hand-off
+## Story template
+(See `wize-create-epics-and-stories` for the canonical template.)
 
-> Story E01-S03 ready. Shuri, pull when sprint allows. Hawkeye, `tea-design.md` for this story whenever you're ready.
+## Rules
+- One story = one PR. If two, split.
+- Each AC must be testable. If Hawkeye can't write a test for it, rewrite the AC.
+- "Out of scope" is mandatory. Force the cut.