Workspace  36898257
└─ Space   PM - Mos            90166731836
   └─ Folder  Zyra World       90169187867  ← the status set is defined here
      └─ List                  901614367195  ← Zyra tasks live here

Tasks use https://app.clickup.com/t/<task-id> — e.g. 86d2wefft is [Module] Virtual Office. Docs under zyra-doc/plan/ reference task ids exactly like that throughout.

Common branches off the happy path

• rejected — the test failed; it bounces back to in progress and runs the loop again from dev
• blocked — can be set from any status when something else is in the way (a design, a decision, another service); when unblocked it returns to where it was
• Work that never reaches production (docs, spikes) may go from accepted straight to closed — PM's call

Status is the team's shared source of truth — whoever moves it must actually know where the work stands.

• Dev owns their stretch: in progress → waitdeploy-dev → completed (and picks work back up from rejected)
• QA owns in review / accepted / rejected / staging
• PM owns the front (open / pending) and the release end (waitdeployed / deployed / closed)

Module-level tasks are named [Module] <name> and contain a scenario table where every scenario has its own id. Those ids are referenced again in specs, test plans and commits.

Each scenario declares a type: Happy Path (the normal flow), Alternate Path (diverges but still succeeds), Error Path (errors or gets blocked).

When you pick up a task

1. Read the whole ClickUp task, including the scenario table and custom fields.
2. Find its companion docs in zyra-doc/plan/<Feature>/ — spec, technical design, test plan, figma-nodes.
3. Branch feat/<name> off develop and build exactly what the spec says.
4. Post progress as comments on the task any time — but leave the status to PM/QA.

Before writing or changing any UI you must pull the spec from the Figma MCP — never guess (.claude/rules/10-figma-fidelity.md).

1. get_design_context(nodeId)   → layout, spacing, colours, typography, padding, gap
2. get_screenshot(nodeId)       → a visual reference to confirm the whole
3. get_variable_defs()          → design tokens
4. get_metadata(nodeId)         → the child tree, for breaking out components

If the node is an instance, expand the main component too. You need the full spec: layout (direction, gap, padding, align), size, colours (hex + alpha), typography (size, weight, line-height, letter-spacing), per-corner border-radius when they differ, effects (shadow, opacity), and states (hover / active / disabled).

Figma → Tailwind

px      → arbitrary value:  p-[16px]  gap-[13px]  w-[368px]
hex     → exact:            bg-[#242B32]  text-[#58D68D]
opacity → rgba:             bg-[rgba(255,255,255,0.05)]
border  → border border-[rgba(255,255,255,0.2)]
font    → text-[14px] leading-[18px] font-bold
radius  → rounded-[8px]  rounded-[16px]