Results for “business-card”

Design or revise a company's commercial policy governing discounts, approver thresholds, exception flows, and deal frameworks using data-backed matrices and linting tools.

Provides evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflows for sales snapshots, pricing comparisons, duplicate-charge diagnosis, or code-backed billing reality.

Routes commercial inquiries to specialized sub-skills for pricing, deal desk, partnerships, channel economics, policy, RFP response, and forecasting. Provides deterministic decision support with canon-cited analysis and human-approver routing.

Create OR review a page-brief — the artifact BETWEEN a wireflow and the full PRD. It turns each unique page/screen of a product into documented requirements TIED TO JOBS: a self-contained board card per page (what the page is accountable for, the job-tagged checklist of what it must let you do, the journeys it appears in, what it connects to, and the acceptance criteria that say how you'd know it's right). It is the "PRD per page", not a sitemap — and it stops ABOVE the screen: no components, no layout, no hierarchy. Use whenever the user wants to "spec the pages", "document each screen", turn a wireflow + live design into per-page requirements, or asks "what does this page need to do / which jobs pass through it" — even if they never say "page-brief". Natural NEXT STEP after the wireflow skill. ALSO use it to REVIEW an existing page-brief / screen catalog. In the A-Team pipeline this is a definition-phase skill: output lands in docs/features/<slug>/briefs/pages/, job codes are the durable [[NN]] ids from doc