arthai-marketplace

/deliverable-builder

Build client-ready consulting deliverables.

Synopsis

/deliverable-builder <client-name> [--type final-report|status-update|board-deck|implementation-guide|training-plan|change-management|data-strategy]

When to use it

• Assembling polished documents from engagement data, final reports, board decks, technical guides
• Producing periodic status updates or plans (training, change management, data strategy) during delivery
• Not for: pre-sale documents like proposals and pitch decks, that’s /pitch-generator; or live progress dashboards, that’s /engagement-tracker

Prerequisites

• A client profile at clients/<client-name>/profile.json
• Engagement data under clients/<client-name>/ (discovery, assessment, architecture, tracking subdirectories), typically produced by running /client-discovery, /opportunity-map, /solution-architect, and /engagement-tracker for the client first
• Without this data, generated deliverables will have thin or empty sections

Quickstart

/deliverable-builder acme-corp --type final-report

What you’ll see: a 12-section engagement report (executive summary through appendices) assembled from the client’s discovery, assessment, architecture, and tracking data, written to clients/acme-corp/deliverables/final-report.md with word count and section list reported.

Examples

/deliverable-builder acme-corp                              # no type — prompts you to choose one
/deliverable-builder acme-corp --type final-report          # 15-30 page comprehensive engagement report
/deliverable-builder acme-corp --type board-deck            # 10-slide executive/board presentation outline
/deliverable-builder acme-corp --type status-update         # 2-5 page periodic progress report
/deliverable-builder acme-corp --type implementation-guide  # 10-20 page technical how-to for IT teams

Arguments & flags

Flag	Values	Default	What it does
--type	final-report status-update board-deck implementation-guide training-plan change-management data-strategy	prompts you	Which deliverable to build

What it does

1. Loads engagement context, reads all available data under clients/<client-name>/ (profile, discovery, assessment, architecture, tracking, prior deliverables) and extracts company name, engagement dates, primary contact, and initiative names.
2. Type selection, user-confirmation checkpoint: if --type was not given, it asks you to choose from the 7 deliverable types.
3. Generates the deliverable from the standard template for that type, pulling content from prior skill outputs:
   • final-report, 12 sections for the executive sponsor: summary, methodology, current state, market analysis, recommendations, architecture, roadmap, ROI, risks, next steps, appendices
   • status-update. RAG status by workstream, accomplishments, risks, decisions needed, next-period plan, key metrics
   • board-deck, 10-slide outline ending in a specific ask and budget approval request
   • implementation-guide, prerequisites checklists, step-by-step setup, configuration reference, testing, runbook, rollback procedures
   • training-plan, skills assessment, three-track curriculum (all staff / power users / technical team), timeline, resources, success metrics
   • change-management, stakeholder analysis, phased communication plan, resistance management, adoption metrics, support structure
   • data-strategy, data landscape and maturity, governance framework, quality standards, migration plan, AI-specific data requirements
4. Quality gates, structure (version header, date, executive summary, TOC), content (citations, valid Mermaid, specific action items, realistic numbers), formatting (no leftover placeholders), and completeness checks before finalizing.
5. Versioned output, if the file already exists, the version number is incremented (1.0 → 1.1) and a change log entry added rather than silently overwriting.

Output & artifacts

• clients/<client-name>/deliverables/<type>.md, the generated deliverable
• A confirmation in the conversation: file path, word count, sections generated, and any quality-gate items needing manual review

Troubleshooting

Problem	Fix
Deliverable has thin or empty sections	The source data is missing: run the upstream skills (discovery, opportunity-map, solution-architect, engagement-tracker) for that client first
Want to regenerate without losing the previous version	Just re-run: the skill bumps the version and adds a change-log entry instead of overwriting
Quality gate flags items for manual review	Address the listed items (usually unsourced numbers or unfilled brackets) before sending to the client

Related

• /consulting, the engagement orchestrator; runs this as the deliver phase
• /pitch-generator, pre-sale counterpart: proposals and pitch documents
• /engagement-tracker, source of the tracking data behind status updates
• /solution-architect, source of the architecture content in reports and guides
• /templates, generic structured documents outside a client engagement