Skip to content

borghei/Claude-Skills / project-management/execution/wayfinder

wayfinder

Verified

Chart work too big for one sprint as a map of decision tickets, resolve them in dependency order, then turn answers into tracer-bullet tickets. Use when the route is unclear, open questions block each other, or estimates swing wildly.

assets/sample_decision_map_clean.json

View on GitHub
{
  "map": "Usage-based billing for self-serve",
  "destination": "New self-serve workspaces are billed per active seat-hour through the new metering pipeline, and every invoice reconciles to the ledger within 0.5% before month-end close.",
  "notes": "Finance owns reconciliation rules. Legacy flat-rate customers stay on the old invoicer until a separate migration effort. One decision per working session; record the answer on the ticket and one line in Decisions so far.",
  "decisions_so_far": [
    {"ticket": "D1", "gist": "Meter on seat-hours aggregated hourly, not raw events."},
    {"ticket": "D2", "gist": "Price in the billing provider; we send usage, they rate it."},
    {"ticket": "D3", "gist": "Rename account_id to workspace_id with expand-migrate-contract before metering ships."}
  ],
  "fog": [
    "How proration works when a workspace changes plan mid-cycle — depends on the provider's rating model (D2) and the dunning policy (D5).",
    "Whether usage alerts go to the workspace owner or the billing contact."
  ],
  "out_of_scope": [
    {"item": "Migrating legacy flat-rate customers", "reason": "Destination covers new self-serve workspaces only; legacy migration is its own effort."},
    {"item": "Multi-currency invoicing", "reason": "Self-serve is USD-only this year."}
  ],
  "tickets": [
    {"id": "D1", "kind": "decision", "type": "discussion", "title": "Unit of metering",
     "question": "What unit do we meter and bill on?",
     "options": ["Raw API events", "Seat-hours aggregated hourly", "Daily active seats"],
     "owner": "Priya (PM)", "status": "resolved", "decide_by": "2026-10-20", "blocked_by": [],
     "resolution": "Seat-hours aggregated hourly. Raw events are too noisy to explain on an invoice; daily seats under-bill bursty teams."},
    {"id": "D2", "kind": "decision", "type": "research", "title": "Where pricing logic lives",
     "question": "Do we rate usage ourselves or send usage to the billing provider to rate?",
     "options": ["Rate in-house", "Provider rates usage"],
     "owner": "Marco (Eng lead)", "status": "resolved", "decide_by": "2026-10-24", "blocked_by": ["D1"],
     "resolution": "Provider rates usage. Its metered-price API covers seat-hours with tiers; in-house rating would duplicate tax and invoicing logic."},
    {"id": "D3", "kind": "decision", "type": "discussion", "title": "Identifier for billable entity",
     "question": "Which identifier keys usage records, given account_id is overloaded?",
     "options": ["Keep account_id", "Rename to workspace_id first"],
     "owner": "Marco (Eng lead)", "status": "resolved", "decide_by": "2026-10-27", "blocked_by": [],
     "resolution": "Rename to workspace_id using expand-migrate-contract so no caller breaks mid-way."},
    {"id": "D4", "kind": "decision", "type": "prototype", "title": "Invoice line presentation",
     "question": "How should seat-hour usage appear on the invoice so customers can check it?",
     "options": ["One line per seat", "One line per day with seat-hour totals", "Single total with downloadable CSV"],
     "owner": "Ana (Design)", "status": "open", "decide_by": "2026-11-14", "blocked_by": ["D2"]},
    {"id": "D5", "kind": "decision", "type": "discussion", "title": "Dunning on failed usage invoices",
     "question": "What happens to a workspace when a usage invoice fails to collect?",
     "options": ["Suspend after 7 days", "Downgrade to free tier after 14 days", "Notify only"],
     "owner": "Lena (Finance)", "status": "claimed", "claimed_by": "Lena", "decide_by": "2026-11-12", "blocked_by": ["D2"]},
    {"id": "D6", "kind": "decision", "type": "enabling-task", "title": "Sandbox account with provider",
     "question": "Can we obtain a provider sandbox with metered prices enabled so D4 can be prototyped against real invoices?",
     "owner": "Marco (Eng lead)", "status": "open", "decide_by": "2026-11-10", "blocked_by": ["D2"]},

    {"id": "R1", "kind": "implementation", "title": "Add workspace_id alongside account_id",
     "pattern": "expand", "refactor_group": "workspace-id-rename", "derived_from": ["D3"], "blocked_by": [],
     "status": "done", "acceptance_criteria": ["Every usage-writing call accepts workspace_id and account_id and stores both", "Existing test suite passes with no caller changes"]},
    {"id": "R2", "kind": "implementation", "title": "Move metering callers to workspace_id",
     "pattern": "migrate", "refactor_group": "workspace-id-rename", "derived_from": ["D3"], "blocked_by": ["R1"],
     "status": "in-progress", "acceptance_criteria": ["No metering caller passes account_id", "Suite passes after the batch"]},
    {"id": "R3", "kind": "implementation", "title": "Move admin and reporting callers to workspace_id",
     "pattern": "migrate", "refactor_group": "workspace-id-rename", "derived_from": ["D3"], "blocked_by": ["R1"],
     "status": "open", "acceptance_criteria": ["No admin or reporting caller passes account_id", "Suite passes after the batch"]},
    {"id": "R4", "kind": "implementation", "title": "Remove account_id from usage records",
     "pattern": "contract", "refactor_group": "workspace-id-rename", "derived_from": ["D3"], "blocked_by": ["R2", "R3"],
     "status": "open", "acceptance_criteria": ["account_id column dropped from usage records", "Search for account_id in usage code returns zero hits"]},
    {"id": "T1", "kind": "implementation", "title": "One workspace's seat-hours appear as usage at the provider",
     "derived_from": ["D1", "D2"], "blocked_by": ["R4"], "status": "open", "estimate_days": 3,
     "layers": ["event capture", "hourly aggregation job", "provider usage API client", "integration test"],
     "demo": "Activate two seats in a sandbox workspace for three hours; the provider dashboard shows 6 seat-hours.",
     "acceptance_criteria": ["An hour with 2 active seats reports exactly 2 seat-hours", "A retried aggregation run does not double-report usage", "Failed provider calls are retried and logged with the workspace_id"]},
    {"id": "T2", "kind": "implementation", "title": "Month-end reconciliation report for metered workspaces",
     "derived_from": ["D2"], "blocked_by": ["T1"], "status": "open", "estimate_days": 2,
     "layers": ["ledger query", "provider invoice export", "report view", "test"],
     "demo": "Finance opens the report for the sandbox month and sees each workspace's billed vs metered seat-hours with variance.",
     "acceptance_criteria": ["Each workspace row shows metered, billed and variance percent", "Rows with variance above 0.5% are highlighted"]}
  ]
}
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall