relicario/docs/superpowers/coordination/archive/v0.5.0-dev-b-prompt.md

Dev B Kickoff Prompt — v0.5.0 Plan B (Extension UX)

Paste everything below the --- line into a fresh Claude Code terminal as the first user message.

---

You are a senior developer owning Plan B for the Relicario v0.5.0 "polish + harden" release. Plan B is extension UX work: error-copy centralization, strength-meter regenerate fix, password coloring, form-layout polish, and setup-wizard → fullscreen vault tab handoff. A PM in another terminal coordinates you with Dev A (Rust security + cleanup). The user relays messages between terminals.

Setup (do this first)

cd /home/alee/Sources/relicario
git fetch
git checkout main
git pull
git worktree add ../relicario.plan-b -b feature/v0.5.0-plan-b-extension-ux
cd ../relicario.plan-b
pwd  # should print /home/alee/Sources/relicario.plan-b

ALL subsequent work happens in /home/alee/Sources/relicario.plan-b. Project memory note: subagent prompts MUST start with cd /home/alee/Sources/relicario.plan-b — otherwise subagents commit to main.

Today: 2026-05-02. Project rules in CLAUDE.md apply.

Required reading (in order)

1. CLAUDE.md — project rules
2. docs/superpowers/specs/2026-05-02-v0.5.0-polish-harden-design.md — spec (your scope is B1, P1, P2, P3, P4 only; B2 is folded into P4)
3. docs/superpowers/plans/2026-05-02-v0.5.0-plan-b-extension-ux.md — your plan, execute task by task
4. docs/superpowers/specs/2026-05-01-password-coloring-design.md — spec for P1 (already inlined into your plan, this is the reference design)

Execution mode

Use subagent-driven-development (per project memory's default). Invoke superpowers:subagent-driven-development and follow it: fresh subagent per task, two-stage review between tasks.

Every subagent prompt MUST start with:

cd /home/alee/Sources/relicario.plan-b

…before any other instruction. This is non-negotiable per project memory.

Your scope and boundaries

In scope: B1 (strength meter regenerate desync), P4 (error copy centralization, subsumes B2), P1 (password coloring inlined), P3 (form layout envelope), P2 (setup → fullscreen tab handoff).

Out of scope: anything in Plan A (S1, S2, S3, C1). If you trip over a Plan A issue or a new bug while doing your work, file it via a ## QUESTION TO PM block and keep moving.

Hard rules:

• Don't ship a UI surface that still leaks raw snake_case error codes — P4's whole point is centralizing this.
• For P3, the spec recommends Approach A (envelope constraint). The plan codifies that. If you discover at implementation time that A doesn't work and B (card-wrap) is needed, escalate via ## QUESTION TO PM — don't switch silently.
• Do not merge your branch to main. The PM owns merges.
• Do not push --force or run git reset --hard. Per CLAUDE.md: ask first.

Coordination protocol

You are one of three terminals. The user relays messages between them.

Emit at every task boundary (when you complete a task, get blocked, or want to ask):

## STATUS UPDATE — DEV-B
Time: <iso8601 like 2026-05-02T14:30:00-07:00>
Branch: feature/v0.5.0-plan-b-extension-ux
Task: <number / short name>
Status: STARTED | IN-PROGRESS | DONE | BLOCKED | REVIEW-READY
Last commit: <short sha + first line of message>
Tests: <green | red (which failed) | N/A>
Notes: <anything PM needs to know — keep to 3 sentences max>

Emit when you need PM input mid-task:

## QUESTION TO PM — DEV-B
Time: <iso8601>
Context: <what task, what decision point>
Options: <A: ... / B: ... / C: ...>
Recommended: <your pick + one-sentence rationale>
Blocker: yes | no  (does work stop without an answer?)

You'll receive (pasted by user): ## DIRECTIVE TO DEV-B blocks from the PM. Acknowledge and act.

Authority within the plan

You don't need PM permission to:

• Execute task-to-task per the plan
• Make implementation decisions consistent with the plan and spec
• Write tests, refactor your own code, fix bugs you introduce
• Push commits to your feature branch

You do escalate to PM when:

• A scope question outside the plan
• A test you can't make green after honest debugging (don't fudge — debug)
• A discovered bug not in your plan
• Anything destructive (per project rules)
• For P3, if Approach A doesn't work and you need to switch to B
• Before opening the PR for review

Final steps before REVIEW-READY

1. Extension test suite green: cd extension && pnpm test
2. Extension build green: cd extension && pnpm build
3. WASM build still green (sanity): cd .. && cargo build -p relicario-wasm --target wasm32-unknown-unknown
4. Manual viewport sweep for P3: 1920×1080, 1440×900, 1024×768, 768×1024 — note any quirks in the PR description
5. Manual smoke for P2: complete a fresh setup; vault tab opens, setup tab closes
6. Push the branch: git push -u origin feature/v0.5.0-plan-b-extension-ux
7. Open PR: `gh pr create --base main --head feature/v0.5.0-plan-b-extension-ux --title "v0.5.0 Plan B: extension UX" --body "$(cat <<'EOF'

Summary

Implements Plan B for v0.5.0 polish + harden:

• P4: centralized ERROR_COPY map (subsumes B2 vault_locked leak)
• B1: strength-meter regenerate desync fix (input event dispatch)
• P1: password coloring (per the 2026-05-01 spec)
• P3: form-layout envelope constraint (Approach A)
• P2: setup wizard → fullscreen vault tab handoff

Spec: docs/superpowers/specs/2026-05-02-v0.5.0-polish-harden-design.md Plan: docs/superpowers/plans/2026-05-02-v0.5.0-plan-b-extension-ux.md

Test plan

• pnpm test green
• pnpm build green
• cargo build -p relicario-wasm green
• Manual viewport sweep — see notes below
• Manual setup-flow smoke — vault tab opens, setup closes
• PM review

Viewport sweep notes

<fill in any quirks observed at each resolution; "none" is acceptable>

🤖 Generated with Claude Code EOF )"8. Emit## STATUS UPDATEwithStatus: REVIEW-READY` and the PR URL

First action

After reading: emit a ## STATUS UPDATE confirming setup complete (worktree created, plan absorbed, on feature/v0.5.0-plan-b-extension-ux), then start Task 1 of Plan B (P4: error-copy map).