Sales Proposals — Reusable-Asset Audit (Arm b)

Sales Proposals — Reusable-Asset Audit (Arm b)

This audit catalogues reusable assets across four source buckets that could be drawn into the planned Knowledge Hub sales-proposals workspace (gap-tracker §D.1 §9.2). §1 enumerates every asset; §2 assesses each one against the seven §9.2 components: ROI calculator, case-study selector, quote picker, pricing configurator, templates, assembly logic, export.

The §9.2 component set as referenced throughout:

• ROI — ROI calculator
• CaseStudy — case-study selector
• Quote — quote picker
• Pricing — pricing configurator
• Templates — templates
• Assembly — assembly logic
• Export — export

---

§1 — Reusable-asset inventory

Bucket 1 — ai-smb-playbook (/Users/liamj/Documents/development/ai-smb-playbook/)

1A — starter-kit/skills (canonical exportable skill library)

Path	Type	Purpose	Maturity
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/agent-browser/	skill	Automate browser interactions for testing, form filling, screenshots, data extraction.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/ast-grep/	skill	Translate natural-language queries into ast-grep rules for structural code search.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/brainstorming/	skill	Explore intent, requirements, and design through collaborative dialogue before implementation.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/brand-review/	skill	Review content against configured brand voice/style guidelines and flag deviations.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/brand-voice/	skill	Document, apply, and enforce brand voice and style guidelines across content.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/canvas-design/	skill	Create static visual art (.png/.pdf) from a written design philosophy.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/claude-md-improver/	skill	Audit and improve CLAUDE.md files across a repository.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/context-engineering-collection/	skill	Reference patterns for context engineering and multi-agent architectures.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/file-organizer/	skill	Organise files and folders, find duplicates, suggest structures, automate cleanup.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/markdown-converter/	skill	Convert PDF/DOCX/PPTX/XLSX/HTML/CSV/JSON/images/audio/ZIP/URL to Markdown via markitdown.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/mcp-builder/	skill	Build production-grade MCP servers (Python FastMCP or TypeScript SDK).	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/mermaid-diagrams/	skill	Author Mermaid diagrams of all common types (flowchart, sequence, ERD, C4, gantt, etc.).	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/prompt-engineering-patterns/	skill	Reference patterns for production prompt design and optimisation.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/proposal-writer/	skill	Sales-proposal strategist with rules for structure, executive summary, pricing, ROI, SOW, RFP, design, follow-up.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/session-handoff/	skill	Generate a continuation prompt to preserve context across sessions.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/uk-english/	skill	Enforce UK English spelling, grammar, and conventions across all output.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/writing-plans/	skill	Convert specs/requirements into ordered task plans before code touches.	production
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/skills/writing-skills/	skill	Author and verify new skill packages prior to deployment.	production

1B — .claude/skills (active overlay; rows below are unique to this overlay, not duplicating starter-kit copies above)

Path	Type	Purpose	Maturity
/Users/liamj/Documents/development/ai-smb-playbook/.claude/skills/playbook-review/	skill	Spawn parallel review agents to audit a client-specific playbook deployment, produce GO/NO-GO report.	production
/Users/liamj/Documents/development/ai-smb-playbook/.claude/skills/skill-development/	skill	Guidance for authoring skills with progressive disclosure inside a Claude Code plugin.	draft
/Users/liamj/Documents/development/ai-smb-playbook/.claude/skills/client-onboarding/	skill	Two-phase guided extraction of client config from training transcript + website into validated ClientConfig JSON.	production
/Users/liamj/Documents/development/ai-smb-playbook/.claude/skills/vercel-react-best-practices/	skill	Vercel Engineering performance patterns for React/Next.js code.	production
/Users/liamj/Documents/development/ai-smb-playbook/.claude/skills/frontend-design/	skill	Build production-grade frontend interfaces avoiding generic AI aesthetics.	production

Note: .claude/skills/{agent-browser, ast-grep, brand-voice, canvas-design, markdown-converter, ...} largely mirror the starter-kit copies of the same name and are not re-listed; treat the starter-kit copy as canonical for assessment.

1C — .agents/skills (consultant-side knowledge skill)

Path	Type	Purpose	Maturity
/Users/liamj/Documents/development/ai-smb-playbook/.agents/skills/assistant-capabilities/	skill	Up-to-date Claude capabilities reference (models, context limits, tool use, platforms, plugins, MCP).	production

1D — Commands

Path	Type	Purpose	Maturity
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/commands/brand-review.md	command	Slash command wrapping the brand-review skill — accepts content + optional guidelines.	production
/Users/liamj/Documents/development/ai-smb-playbook/.claude/commands/client-research.md	command	Systematic crawl of a client website + public sources, producing a research document for onboarding.	production
/Users/liamj/Documents/development/ai-smb-playbook/.claude/commands/frontend-design/	command	17-command suite (adapt, animate, audit, bolder, clarify, colorize, critique, delight, extract, harden, normalize, onboard, optimize, polish, quieter, simplify, teach-impeccable) for frontend craft operations.	production

1E — Prompts

Path	Type	Purpose	Maturity
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/prompts/brand-voice-setup-prompt.md	prompt	Initial prompt to capture brand voice for a new client engagement.	template
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/prompts/example-handoff-general.md	prompt	Worked example of a session-handoff continuation prompt for non-technical users.	template
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/prompts/example-handoff-technical.md	prompt	Worked example of a session-handoff continuation prompt for developers/QA.	template

1F — Templates

Path	Type	Purpose	Maturity
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/templates/claude-md-template.md	template	Parameterised CLAUDE.md skeleton for new repositories.	template
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/templates/docs-structure-template.md	template	Recommended docs/ tree layout for a project.	template
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/templates/feasibility-study-template.md	template	Parameterised AI use-case feasibility study aligned to the playbook builder.	template
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/templates/governance-policy-template.md	template	Parameterised AI governance policy for UK SMBs (GDPR/ICO references).	template

1G — gsd-mapper system

Path	Type	Purpose	Maturity
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/gsd-mapper/	other (multi-file system)	Parallel codebase-mapper system — slash command + agent + workflow + 7 codebase output templates (architecture, concerns, conventions, integrations, stack, structure, testing).	production

1H — Vendored Anthropic plugins (sub-marketplace)

Path	Type	Purpose	Maturity
/Users/liamj/Documents/development/ai-smb-playbook/starter-kit/plugins/claude-plugins-official/	other (plugin marketplace bundle)	Vendored snapshot of 14 Anthropic-official plugins: asana, claude-md-management, code-simplifier, coderabbit, commit-commands, context7, example-plugin, github, php-lsp, playwright, plugin-dev, pr-review-toolkit, security-guidance, sentry.	production

1I — Application code (React playbook frontend)

Path	Type	Purpose	Maturity
/Users/liamj/Documents/development/ai-smb-playbook/app/src/lib/docx-export.ts	module	Markdown → DOCX exporter using the docx package — parses headings/bullets/separators/inline runs, builds Word document.	production
/Users/liamj/Documents/development/ai-smb-playbook/app/src/components/content/	module	Content presentation components: CalloutCard, CodeBlock, CopyButton, PromptExample, SectionPage, SetupStepCard, TableOfContents, etc.	production
/Users/liamj/Documents/development/ai-smb-playbook/app/src/components/interactive/	module	Context-window simulator UI components (ContextWindowBar, ContextWindowSimulator, SimulatorControls, SimulatorStatus).	production
/Users/liamj/Documents/development/ai-smb-playbook/app/src/components/layout/	module	App shell layout (AppLayout, Header, Sidebar, Footer, HomePage, TrackLayout, ThemeSettings, ErrorBoundary).	production
/Users/liamj/Documents/development/ai-smb-playbook/app/src/components/ui/	module	Radix-based UI primitive set (button, card, dialog, accordion, alert, tabs, dropdown-menu, tooltip, etc., 18 primitives).	production
/Users/liamj/Documents/development/ai-smb-playbook/app/src/content/general/	module	Section components for the general track: BrandVoiceSection, FeasibilityStudyBuilder, GovernancePolicySection, RecurringTasksSection, RoiMeasurementSection, SessionManagementSection, SkillsExtensionsSection, ContextSimulatorSection, ReliableOutputSection.	production
/Users/liamj/Documents/development/ai-smb-playbook/app/src/config/client-config-schema.ts	module	TypeScript schema + interface for multi-tenant ClientConfig JSON used to swap clients at runtime.	production
/Users/liamj/Documents/development/ai-smb-playbook/app/public/clients/_template.json	template	Reference ClientConfig JSON with placeholder values for new client onboarding.	template
/Users/liamj/Documents/development/ai-smb-playbook/app/api/feedback.ts	module	Vercel function implementing the in-app feedback widget POST endpoint.	production

1J — Docs and delivery assets

Path	Type	Purpose	Maturity
/Users/liamj/Documents/development/ai-smb-playbook/docs/repeatable-workflow.md	other (process doc)	Internal seven-step workflow (record → summarise → plan → spec → build → deploy → deliver) for post-training deliverables.	production
/Users/liamj/Documents/development/ai-smb-playbook/docs/reference/delivery-assets/delivery-email-training.md	template	Client-facing playbook handover email template for training engagements.	template
/Users/liamj/Documents/development/ai-smb-playbook/docs/reference/delivery-assets/delivery-email-advisory.md	template	Client-facing playbook handover email template for advisory engagements.	template
/Users/liamj/Documents/development/ai-smb-playbook/docs/reference/delivery-assets/client-report-example.html	brand-asset	HTML example of a client deliverable report (post-engagement report).	template
/Users/liamj/Documents/development/ai-smb-playbook/docs/reference/delivery-assets/client-report-example.pdf	brand-asset	PDF rendering of the same client deliverable report.	template
/Users/liamj/Documents/development/ai-smb-playbook/docs/reference/	other (research notes)	Reference research docs: application-overview, capabilities-audit, claude-code-capabilities-extension-options, client-onboarding-skill-design, frontend-skills-review, market-research-insights, roi-article-synthesis, smb-context, smb-task-patterns, supertokens-evaluation.	production
/Users/liamj/Documents/development/ai-smb-playbook/docs/design/	brand-asset	Brand assets — aish-logo-light-no-icon.png, AMD-Group-...png, phew-logo-...{png,webp}, client-report.html, screenshot.	production

1K — Scripts

Path	Type	Purpose	Maturity
/Users/liamj/Documents/development/ai-smb-playbook/scripts/build-skill-zips.sh	script	Builds per-skill ZIP files into app/public/starter-kit/zips/ for download from the playbook UI.	production

---

Bucket 2 — Anthropic Sales plugin (.claude/plugins/sales/1.1.0/)

Path	Type	Purpose	Maturity
.claude/plugins/sales/1.1.0/skills/account-research/	skill	Research a company or person; works standalone via web search, supercharged with enrichment + CRM.	production
.claude/plugins/sales/1.1.0/skills/call-prep/	skill	Prepare for a sales call with account context, attendee research, suggested agenda.	production
.claude/plugins/sales/1.1.0/skills/competitive-intelligence/	skill	Research competitors and emit an interactive HTML battlecard artefact.	production
.claude/plugins/sales/1.1.0/skills/create-an-asset/	skill	Generate landing pages / decks / one-pagers / workflow demos tailored to deal context.	production
.claude/plugins/sales/1.1.0/skills/daily-briefing/	skill	Prioritised daily sales briefing across calendar/CRM/email signals.	production
.claude/plugins/sales/1.1.0/skills/draft-outreach/	skill	Research-then-draft personalised outreach (email/message).	production
.claude/plugins/sales/1.1.0/commands/call-summary.md	command	Process call notes/transcripts → action items, follow-up email, internal summary.	production
.claude/plugins/sales/1.1.0/commands/forecast.md	command	Weighted sales forecast with best/likely/worst, commit vs upside, gap analysis.	production
.claude/plugins/sales/1.1.0/commands/pipeline-review.md	command	Pipeline health analysis with prioritisation, risk flags, weekly action plan.	production
.claude/plugins/sales/1.1.0/.claude-plugin/	other (plugin manifest)	Plugin manifest folder defining the plugin name, version, contents.	production
.claude/plugins/sales/1.1.0/.mcp.json	other (MCP config)	MCP-server configuration declaring connectors used by the plugin.	production
.claude/plugins/sales/1.1.0/CONNECTORS.md	other (docs)	Connector reference doc describing the optional integrations (CRM, email, calendar).	production
.claude/plugins/sales/1.1.0/README.md	other (docs)	Plugin README.	production
.claude/plugins/sales/1.1.0/LICENSE	other (legal)	Plugin licence text (Anthropic).	production

---

Bucket 3 — Local KH skills (.claude/skills/, excluding proposal-writer/ and the sales bucket)

Path	Type	Purpose	Maturity
.claude/skills/ast-grep/	skill	ast-grep guidance for structural code search (mirror of starter-kit version).	production
.claude/skills/handoff/	skill	Knowledge-Hub-flavoured continuation-prompt generator; structured for KH session conventions.	production
.claude/skills/review/	skill	Reads .claude/checks/ and produces pass/fail report on the diff against KH standards.	production
.claude/skills/start-session/	skill	Cleans up worktrees, reads critical KH docs, prompts for continuation paste.	production
.claude/skills/update-docs/	skill	Updates roadmap, state-of-the-product, generated stats, backlog after a KH session and chains to handoff.	production

---

Bucket 4 — proposal-writer skill (.claude/skills/proposal-writer/)

The single skill is the asset surface; SKILL.md is the entry point and rules/ holds 11 topical rule files invoked by the skill.

Path	Type	Purpose	Maturity
.claude/skills/proposal-writer/SKILL.md	skill	Top-level skill — defines philosophy (“describe buyer’s future success”), the Proposal Pyramid (Exec / Solution / Investment / Proof), and dispatches to rules/.	production
.claude/skills/proposal-writer/rules/structure-proposal-architecture.md	other (rule)	CRITICAL — winning proposal structure (sections, page budgets, reader-by-section).	production
.claude/skills/proposal-writer/rules/structure-terms-conditions.md	other (rule)	HIGH — terms & conditions positioning (legal as part of negotiation, not afterthought).	production
.claude/skills/proposal-writer/rules/executive-summary-writing.md	other (rule)	CRITICAL — one-page executive summary that compels action in 2-3 minutes.	production
.claude/skills/proposal-writer/rules/executive-stakeholder-alignment.md	other (rule)	HIGH — equipping the champion with materials to sell internally to the buying committee.	production
.claude/skills/proposal-writer/rules/pricing-presentation.md	other (rule)	CRITICAL — anchoring, packaging, never showing price before establishing value.	production
.claude/skills/proposal-writer/rules/pricing-roi-business-case.md	other (rule)	CRITICAL — business case framework arming the champion with internal-ROI justification.	production
.claude/skills/proposal-writer/rules/sow-writing.md	other (rule)	HIGH — Statement of Work scope, deliverables, contractual implementation language.	production
.claude/skills/proposal-writer/rules/rfp-response-strategy.md	other (rule)	HIGH — RFP/bid response best practice, compliance, win-themes.	production
.claude/skills/proposal-writer/rules/design-formatting.md	other (rule)	MEDIUM-HIGH — visual hierarchy, formatting, layout, branding for proposals.	production
.claude/skills/proposal-writer/rules/strategy-competitive-differentiation.md	other (rule)	HIGH — competitive differentiation, positioning vs alternatives.	production
.claude/skills/proposal-writer/rules/strategy-followup.md	other (rule)	HIGH — follow-up cadence, closing patterns, objection handling, negotiation.	production

---

§2 — Per-asset assessment

Bucket 1 — ai-smb-playbook

starter-kit/skills/agent-browser/

• What it does today: Drives agent-browser Bash sub-tool to navigate web pages, fill forms, take screenshots, and extract content. Backed by an isolated browser session so concurrent runs do not collide.
• Fit: Low — proposal assembly is internal data plus templating; live web automation is not on the §9.2 critical path.
• Gaps to close: None to “use” it; would need a clear user-story (e.g. scrape a target customer’s website to seed proposal context) to justify the dependency.
• Effort: XS to wire into KH skills tree.
• Maps to §9.2: none directly. Could indirectly support CaseStudy if used to verify case-study URL freshness.

starter-kit/skills/ast-grep/

• What it does today: Translates natural language into structural AST search rules across a codebase.
• Fit: No-fit — code-search skill, no proposal-workspace use case.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

starter-kit/skills/brainstorming/

• What it does today: Pre-implementation dialogue skill — explores intent, requirements, design before code.
• Fit: Medium — applies to designing the §9.2 workspace itself rather than to the runtime proposal flow; would help intake conversations where the user describes a new opportunity.
• Gaps to close: None to use; could be instructed to dispatch to the proposal-writer skill when the brainstorm clarifies the user wants a proposal.
• Effort: XS.
• Maps to §9.2: Assembly (intake stage of proposal authoring).

starter-kit/skills/brand-review/

• What it does today: Reviews content against configured brand voice/style guide and flags deviations with suggestions.
• Fit: High — proposals MUST land on-brand; this is the natural QA pass before export.
• Gaps to close: Needs the KH brand voice configured as the guide source (currently expects a file/Notion reference). Should run automatically after assembly.
• Effort: S (configure guidelines source + add assembly hook).
• Maps to §9.2: Assembly (post-assembly QA), Templates (template lint).

starter-kit/skills/brand-voice/

• What it does today: Frameworks for documenting and applying brand voice — pillars, tone-by-audience, terminology, do/don’t lists.
• Fit: High — defines what brand-review enforces; both must use the same source.
• Gaps to close: Must be connected to the KH brand-voice document; currently an authoring framework rather than a runtime data source.
• Effort: S (document the KH brand voice using its framework, persist as a referenced file).
• Maps to §9.2: Templates (voice rules baked into templates), Assembly (voice enforcement at section level).

starter-kit/skills/canvas-design/

• What it does today: Generates static visual art (.png/.pdf) from a written design philosophy. Two-step flow (philosophy → expression).
• Fit: Low — relevant if proposals need bespoke cover artwork; not in the §9.2 component set as scoped.
• Gaps to close: Would need a brand-aligned design philosophy as the input.
• Effort: S to integrate, but unscored against §9.2.
• Maps to §9.2: none directly.

starter-kit/skills/claude-md-improver/

• What it does today: Audits and improves CLAUDE.md files repository-wide.
• Fit: No-fit — repo-meta tool; no proposal use.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

starter-kit/skills/context-engineering-collection/

• What it does today: Reference patterns for context engineering, multi-agent architectures, production agent systems.
• Fit: Medium — informs how the §9.2 assembly logic itself is built (orchestrator pattern across selectors and pickers), not the runtime artefact.
• Gaps to close: None to read; it is a reference.
• Effort: XS (consult during design).
• Maps to §9.2: Assembly (architectural reference).

starter-kit/skills/file-organizer/

• What it does today: Organises file/folder structure, finds duplicates.
• Fit: No-fit.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

starter-kit/skills/markdown-converter/

• What it does today: Converts PDF/DOCX/PPTX/XLSX/HTML/CSV/JSON/images/audio/ZIP to Markdown via uvx markitdown.
• Fit: Medium — useful for ingesting prospect-supplied RFP documents (PDF/DOCX) into Markdown the workspace can parse and respond against.
• Gaps to close: Needs markitdown available on the KH environment; needs an entry-point for “ingest this RFP” path.
• Effort: S (env install + entry path; conversion itself is a single CLI).
• Maps to §9.2: Assembly (RFP ingestion preprocessing).

starter-kit/skills/mcp-builder/

• What it does today: Production guidance for building MCP servers (Python FastMCP or TS SDK).
• Fit: Medium — relevant if the proposals workspace exposes MCP tools (e.g. quote_picker, roi_calculator) so external clients can compose proposals through Claude Desktop.
• Gaps to close: Decide whether the workspace exposes MCP tools at all (a workspace decision, not in this audit).
• Effort: M to design and ship MCP tools for the workspace; XS to consult the skill while doing so.
• Maps to §9.2: Assembly (if MCP-driven), Quote, Pricing, ROI (if exposed as discrete tools).

starter-kit/skills/mermaid-diagrams/

• What it does today: Reference for authoring Mermaid diagrams of all common types.
• Fit: Medium — proposals frequently include process flows, organisation maps, integration diagrams; this reduces effort to embed them.
• Gaps to close: Need a render path in the chosen export format (HTML embeds; DOCX needs SVG/PNG conversion).
• Effort: S.
• Maps to §9.2: Templates (diagram blocks), Export (rendering pipeline).

starter-kit/skills/prompt-engineering-patterns/

• What it does today: Production prompt-design patterns reference.
• Fit: Medium — applies to the prompts inside the workspace’s assembly logic.
• Gaps to close: None to read.
• Effort: XS (consult during design).
• Maps to §9.2: Assembly (prompt design reference).

starter-kit/skills/proposal-writer/

• What it does today: This is also Bucket 4. Treated authoritatively in §2 Bucket 4 below to avoid duplicate assessment.
• Fit: High — see Bucket 4.
• Gaps to close: See Bucket 4.
• Effort: See Bucket 4.
• Maps to §9.2: Templates, Assembly, ROI, Pricing, Quote.

starter-kit/skills/session-handoff/

• What it does today: Generates a continuation prompt to preserve context across sessions.
• Fit: Low — workspace-internal, not user-facing.
• Gaps to close: None.
• Effort: XS.
• Maps to §9.2: none.

starter-kit/skills/uk-english/

• What it does today: Enforces UK English spelling and conventions across all output.
• Fit: High — KH standard is UK English; proposals must comply.
• Gaps to close: Should auto-load on every proposal generation step, not by trigger.
• Effort: XS (already an established pattern in KH).
• Maps to §9.2: Templates (template content), Assembly (output normalisation).

starter-kit/skills/writing-plans/

• What it does today: Converts a spec into ordered task plans before code touches.
• Fit: Medium — applies to building the workspace, not the runtime.
• Gaps to close: None.
• Effort: XS (consult during design).
• Maps to §9.2: none directly.

starter-kit/skills/writing-skills/

• What it does today: Frameworks for authoring and verifying skill packages.
• Fit: Medium — applies to the building of the workspace’s own skills (e.g. a future /draft-proposal).
• Gaps to close: None.
• Effort: XS (consult during design).
• Maps to §9.2: Assembly (if §9.2 ships its own skill).

.claude/skills/playbook-review/ (asip overlay)

• What it does today: Spawns parallel review agents to audit a client-specific playbook deployment, produces GO/NO-GO report.
• Fit: Medium — analogous to a “proposal-readiness review” before sending. Pattern transfers; specific checks do not.
• Gaps to close: Replace playbook-specific check files with proposal-readiness checks (compliance, branding, pricing-sanity, signoffs).
• Effort: M (rewrite checks; pattern reuse is fast).
• Maps to §9.2: Assembly (pre-send gate).

.claude/skills/skill-development/ (asip overlay)

• What it does today: Guidance for authoring skills inside a Claude Code plugin.
• Fit: Medium — applies to building the workspace’s own skills.
• Gaps to close: None.
• Effort: XS.
• Maps to §9.2: none directly.

.claude/skills/client-onboarding/ (asip overlay)

• What it does today: Two-phase guided extraction of client config (transcript + website) into validated ClientConfig JSON.
• Fit: High — directly transferable pattern: a guided extractor that produces structured client data is exactly what intake → assembly needs. Repurposable as a “proposal-onboarding” skill that yields a typed ProposalContext.
• Gaps to close: New schema (ProposalContext), new sources (deal context vs. training transcript), new validations.
• Effort: M (rewrite for proposals domain; structural pattern reuses).
• Maps to §9.2: Assembly (intake), CaseStudy (inputs to selector), Pricing (inputs to configurator).

.claude/skills/vercel-react-best-practices/ (asip overlay)

• What it does today: Vercel performance patterns for React/Next.js.
• Fit: Medium — applies if §9.2 has interactive UI in KH (Next.js).
• Gaps to close: None.
• Effort: XS.
• Maps to §9.2: none directly.

.claude/skills/frontend-design/ (asip overlay)

• What it does today: Build production-grade frontend interfaces avoiding generic AI aesthetics.
• Fit: Medium — applies if the workspace UI is built in KH.
• Gaps to close: None.
• Effort: XS.
• Maps to §9.2: none directly (informs UI build).

.agents/skills/assistant-capabilities/

• What it does today: Up-to-date Claude capabilities reference (models, contexts, tools, platforms, plugins, MCP).
• Fit: Low — meta-reference, not part of the proposals data flow.
• Gaps to close: None.
• Effort: N/A.
• Maps to §9.2: none.

starter-kit/commands/brand-review.md

• What it does today: Slash command wrapping the brand-review skill — accepts content + optional guidelines.
• Fit: High — the natural pre-export QA command for proposals.
• Gaps to close: Default-to KH brand voice when invoked from the proposals workspace.
• Effort: XS (parameter default).
• Maps to §9.2: Assembly (QA gate), Templates (template-level lint).

.claude/commands/client-research.md

• What it does today: Systematic crawl of a client website + public sources, producing a research document for onboarding.
• Fit: High — direct analogue of “research the prospect before drafting” for the proposals workflow; output is exactly the kind of context the assembly logic needs.
• Gaps to close: Output schema needs to match ProposalContext rather than the playbook’s ClientConfig.
• Effort: S (schema swap; crawl pattern reuses).
• Maps to §9.2: Assembly (intake), CaseStudy (sector/use-case signal).

.claude/commands/frontend-design/ (17 commands)

• What it does today: Frontend craft suite — adapt, animate, audit, bolder, clarify, colorize, critique, delight, extract, harden, normalize, onboard, optimize, polish, quieter, simplify, teach-impeccable.
• Fit: Low — these are interactive UI craft operations on a frontend. Useful when building the workspace’s UI, not at proposal runtime.
• Gaps to close: None.
• Effort: XS (already invokable).
• Maps to §9.2: none directly (informs UI build).

starter-kit/prompts/brand-voice-setup-prompt.md

• What it does today: Initial prompt to capture brand voice for a new client engagement.
• Fit: High — same purpose for proposals.
• Gaps to close: Adapt to KH brand voice once and persist.
• Effort: XS.
• Maps to §9.2: Templates (voice as template input).

starter-kit/prompts/example-handoff-general.md

• What it does today: Worked example of a session-handoff continuation prompt for non-technical users.
• Fit: Low — workspace-internal documentation pattern; not user-facing.
• Gaps to close: None.
• Effort: N/A.
• Maps to §9.2: none.

starter-kit/prompts/example-handoff-technical.md

• What it does today: Worked example of a session-handoff continuation prompt for developers/QA.
• Fit: Low — workspace-internal documentation pattern; not user-facing.
• Gaps to close: None.
• Effort: N/A.
• Maps to §9.2: none.

starter-kit/templates/claude-md-template.md

• What it does today: Parameterised CLAUDE.md skeleton for new repositories.
• Fit: No-fit — repo-meta template, not a proposal artefact.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

starter-kit/templates/docs-structure-template.md

• What it does today: Recommended docs/ tree layout for a project.
• Fit: No-fit — repo-meta template.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

starter-kit/templates/feasibility-study-template.md

• What it does today: Parameterised AI use-case feasibility study template (UK SMB-aligned, GBP, DD/MM/YYYY).
• Fit: High — proposals frequently include or annex a feasibility study; the parameterisation pattern is the right shape for the Templates component.
• Gaps to close: Adapt placeholders to the proposals domain (drop {{USE_CASE_NAME}} for a more general project descriptor); add slots for ROI/pricing.
• Effort: S.
• Maps to §9.2: Templates, ROI (the study includes ROI sections).

starter-kit/templates/governance-policy-template.md

• What it does today: Parameterised AI governance policy (GDPR/ICO references, UK SMB context).
• Fit: Medium — useful annex for proposals where governance is a buying criterion (regulated sectors).
• Gaps to close: None to use as-is; adapt placeholder reference to ProposalContext.
• Effort: S.
• Maps to §9.2: Templates.

starter-kit/gsd-mapper/

• What it does today: Parallel codebase-mapper system — slash command + agent + workflow + 7 codebase output templates.
• Fit: No-fit — codebase-mapping system, not a proposal artefact.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

starter-kit/plugins/claude-plugins-official/

• What it does today: Vendored snapshot of 14 Anthropic plugins (asana, claude-md-management, code-simplifier, coderabbit, commit-commands, context7, example-plugin, github, php-lsp, playwright, plugin-dev, pr-review-toolkit, security-guidance, sentry).
• Fit: Low — most are dev-tooling. Only context7 (live library docs) and example-plugin (skill skeleton) might inform building the workspace; none deliver proposal value at runtime.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

app/src/lib/docx-export.ts

• What it does today: Markdown → DOCX exporter using the docx package — parses headings/bullets/separators/inline runs (bold/italic/code/links), builds paragraphs.
• Fit: High — proposals must export to DOCX (the buyer’s format of choice). This is a working starting point that already covers the common Markdown surface.
• Gaps to close: Page styling (cover page, headers/footers, page breaks), table support, image embed, branded heading styles. The current implementation is intentionally minimal.
• Effort: M (extend; library + parsing pattern stays).
• Maps to §9.2: Export.

app/src/components/content/

• What it does today: Content-presentation React components (CalloutCard, CodeBlock, CopyButton, PromptExample, SectionPage, SetupStepCard, TableOfContents, etc.).
• Fit: Medium — analogous components are needed in the workspace UI for previewing proposal sections.
• Gaps to close: Visual restyle to KH’s Warm Meridian; KH already has equivalent primitives so reuse is for the patterns, not the code.
• Effort: S.
• Maps to §9.2: none directly (UI scaffolding).

app/src/components/interactive/

• What it does today: Context-window simulator UI components.
• Fit: No-fit.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

app/src/components/layout/

• What it does today: App shell layout components.
• Fit: No-fit (KH has its own shell).
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

app/src/components/ui/

• What it does today: Radix-based UI primitive set (button, card, dialog, accordion, alert, tabs, dropdown-menu, tooltip etc.).
• Fit: No-fit (KH already has Radix-based primitives).
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

app/src/content/general/ (RoiMeasurementSection, FeasibilityStudyBuilder, etc.)

• What they do today: Section components for the playbook’s general track — including RoiMeasurementSection and FeasibilityStudyBuilder as interactive guided-input tools.
• Fit: High for RoiMeasurementSection and FeasibilityStudyBuilder; medium for the rest.
• Gaps to close: Extract the input → calculation → output pattern; rebind to a proposals data model. The interactive widget pattern (guided input with live preview) is exactly what an in-workspace ROI calculator needs.
• Effort: M (extract + adapt the two relevant components; ignore the others).
• Maps to §9.2: ROI (RoiMeasurementSection, FeasibilityStudyBuilder), Templates (FeasibilityStudyBuilder produces a templated output).

app/src/config/client-config-schema.ts

• What it does today: TypeScript interface for multi-tenant ClientConfig JSON used to swap clients at runtime.
• Fit: High — direct precedent for a typed ProposalContext schema. The shape (siteConfig + content overlays + brand) is the same shape proposals need (deal context + content blocks + brand).
• Gaps to close: Define the proposal-domain fields; reuse the typed-loader pattern.
• Effort: S.
• Maps to §9.2: Assembly (typed inputs), Templates (typed template parameters).

app/public/clients/_template.json

• What it does today: Reference ClientConfig JSON with placeholder values.
• Fit: Medium — example of the placeholder convention worth reusing for ProposalContext.
• Gaps to close: Recreate for the proposals schema once defined.
• Effort: XS.
• Maps to §9.2: Templates (placeholder convention).

app/api/feedback.ts

• What it does today: Vercel function for the in-app feedback widget.
• Fit: No-fit.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

docs/repeatable-workflow.md

• What it does today: Internal seven-step workflow (record → summarise → plan → spec → build → deploy → deliver) for post-training deliverables.
• Fit: Medium — the shape (intake → spec → build → deliver) maps cleanly to a proposals lifecycle (intake → assemble → review → send). Reusable as a thinking aid, not as code.
• Gaps to close: Translate steps to proposals domain.
• Effort: XS (consult during design).
• Maps to §9.2: Assembly (lifecycle reference).

docs/reference/delivery-assets/delivery-email-training.md

• What it does today: Client-facing playbook handover email template for training engagements.
• Fit: Medium — proposals will need a cover-email template at send time. Pattern reuses; content does not.
• Gaps to close: Rewrite copy for proposals; align to KH brand voice.
• Effort: XS.
• Maps to §9.2: Templates (cover email).

docs/reference/delivery-assets/delivery-email-advisory.md

• What it does today: Client-facing playbook handover email template for advisory engagements.
• Fit: Medium — same as the training-engagement variant; the engagement-type variation is a useful pattern in itself (template variants per engagement shape).
• Gaps to close: Rewrite copy for proposals; map engagement variants to proposal types (advisory vs project vs retainer).
• Effort: XS.
• Maps to §9.2: Templates (cover email variants).

docs/reference/delivery-assets/client-report-example.html

• What it does today: HTML example of a finished client deliverable report.
• Fit: Medium — visual reference for how a finished deliverable should feel; useful when designing the Templates look-and-feel and the HTML export style.
• Gaps to close: None to read.
• Effort: XS (visual reference only).
• Maps to §9.2: Templates (visual reference), Export (HTML reference).

docs/reference/delivery-assets/client-report-example.pdf

• What it does today: PDF rendering of the same client deliverable report.
• Fit: Medium — visual reference for the PDF export style.
• Gaps to close: None to read.
• Effort: XS (visual reference only).
• Maps to §9.2: Export (PDF reference).

docs/reference/ (research notes — application-overview, capabilities-audit, smb-context, etc.)

• What they do today: Internal research docs informing the playbook product (market research, ROI articles, SMB task patterns, capabilities audits, competitor evaluations).
• Fit: Medium — roi-article-synthesis and market-research-insights could seed claims/statistics for the CaseStudy and ROI components if they hold defensible data. Treat as raw material rather than reusable surface.
• Gaps to close: Curate which docs (if any) ship into the workspace’s evidence corpus.
• Effort: XS (read), S (curate).
• Maps to §9.2: CaseStudy (sector context), ROI (ROI claim sources).

docs/design/ (logos and report HTML)

• What it does today: Brand assets — client logos (AMD, Phew, AI Solution Hub) and an example HTML client report.
• Fit: Low — client-specific branding; KH proposals would use their own brand assets.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none directly.

scripts/build-skill-zips.sh

• What it does today: Builds per-skill ZIPs into app/public/starter-kit/zips/ for download.
• Fit: Low — ASIP-specific delivery mechanism.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

---

Bucket 2 — Anthropic Sales plugin

account-research/

• What it does today: Researches a company or person — works standalone via web search, supercharged with enrichment + CRM connectors.
• Fit: High — an “intake” step into a proposal needs prospect intelligence; this slot is exactly the right shape.
• Gaps to close: Replace generic web-research output with a structured AccountSnapshot consumable by the assembly logic. Decide CRM connector posture (KH has no CRM today).
• Effort: S to wire as-is, M to formalise the output schema.
• Maps to §9.2: Assembly (intake), CaseStudy (informs sector/use-case match).

call-prep/

• What it does today: Prepares for a sales call with account context, attendee research, suggested agenda.
• Fit: Low — separate sales workflow; not on the proposal-authoring path.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

competitive-intelligence/

• What it does today: Researches competitors, emits an interactive HTML battlecard.
• Fit: Medium — proposals frequently include a competitive-positioning slide. The battlecard HTML pattern is too rich for embed but the underlying competitor data is reusable.
• Gaps to close: Strip HTML output, expose structured competitor records to the assembly logic for templated insertion.
• Effort: M.
• Maps to §9.2: CaseStudy (competitor positioning is adjacent), Assembly (competitive section).

create-an-asset/

• What it does today: Generates landing pages / decks / one-pagers / workflow demos tailored to deal context.
• Fit: Medium-to-High — closest existing analogue to the §9.2 workspace itself. Asset-generation pattern (intake → tailored output) overlaps. But the output formats (landing page, deck) are not the proposals output (DOCX/PDF), so the pattern transfers, not the implementation.
• Gaps to close: Replace HTML/deck generation with proposals templates; replace deal context with ProposalContext.
• Effort: M (pattern reuse, full rewrite of generation step).
• Maps to §9.2: Assembly, Templates.

daily-briefing/

• What it does today: Prioritised daily sales briefing.
• Fit: Low — separate workflow.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

draft-outreach/

• What it does today: Research-then-draft personalised outreach (email/message).
• Fit: Medium — could power a “follow-up email” generator after a proposal is sent (the proposal-writer skill’s strategy-followup rule covers what to say; this provides the run-it-now skill).
• Gaps to close: Wire to a proposal record + recipient context.
• Effort: S.
• Maps to §9.2: Assembly (post-send follow-up).

commands/call-summary.md

• What it does today: Processes call notes/transcripts → action items, follow-up email, internal summary.
• Fit: Medium — discovery calls precede proposals; the structured action-item output feeds intake.
• Gaps to close: Route action items into ProposalContext rather than CRM.
• Effort: S.
• Maps to §9.2: Assembly (intake from discovery).

commands/forecast.md

• What it does today: Weighted sales forecast with best/likely/worst, commit vs upside, gap analysis.
• Fit: Low — pipeline management, not proposal authoring.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

commands/pipeline-review.md

• What it does today: Pipeline health analysis with prioritisation, risk flags, weekly action plan.
• Fit: Low — pipeline management, not proposal authoring.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

.claude-plugin/

• What it does today: Plugin manifest folder declaring plugin identity, version, contents.
• Fit: Low — architectural reference if KH ever ships a sales plugin.
• Gaps to close: N/A.
• Effort: XS (consult).
• Maps to §9.2: none (architectural reference).

.mcp.json

• What it does today: MCP-server configuration declaring connectors used by the plugin.
• Fit: Low — architectural reference; relevant only if the workspace ships an MCP face.
• Gaps to close: N/A.
• Effort: XS (consult).
• Maps to §9.2: none (architectural reference).

CONNECTORS.md

• What it does today: Connector reference doc describing optional integrations (CRM, email, calendar).
• Fit: Low — reference only.
• Gaps to close: N/A.
• Effort: XS.
• Maps to §9.2: none.

README.md

• What it does today: Plugin README.
• Fit: Low — reference only.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

LICENSE

• What it does today: Plugin licence text.
• Fit: No-fit — legal text, not a reusable component.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

---

Bucket 3 — Local KH skills

.claude/skills/ast-grep/

• What it does today: ast-grep guidance for structural code search (mirror of starter-kit version).
• Fit: No-fit for proposals.
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

.claude/skills/handoff/

• What it does today: KH-flavoured continuation-prompt generator.
• Fit: Low (workspace-internal).
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

.claude/skills/review/

• What it does today: Reads .claude/checks/ and produces pass/fail report on the diff against KH standards.
• Fit: Medium — pattern reuse: a checks-driven review is the right shape for a “proposal-readiness” gate. The check files would differ.
• Gaps to close: Author proposal-readiness checks (legal-clauses present, pricing-set, citations-resolved, brand-passes).
• Effort: M (write checks; pattern reuses).
• Maps to §9.2: Assembly (pre-send gate).

.claude/skills/start-session/

• What it does today: Worktree cleanup + critical-doc loading at session start.
• Fit: Low (workspace-internal).
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

.claude/skills/update-docs/

• What it does today: Updates roadmap, state-of-the-product, generated stats, backlog after a session and chains to handoff.
• Fit: Low (workspace-internal).
• Gaps to close: N/A.
• Effort: N/A.
• Maps to §9.2: none.

---

Bucket 4 — proposal-writer skill

SKILL.md (entry point)

• What it does today: Defines proposal philosophy (“describe buyer’s future success”), the four-tier Proposal Pyramid (Executive Summary / Solution / Investment / Proof), and dispatches to the rule files in rules/.
• Fit: High — this is the most directly aligned asset across all four buckets. It is the sales-proposal skill.
• Gaps to close: Today the skill is a strategist’s reference. To power the §9.2 workspace it needs to be wrapped by an assembly orchestrator that picks up ProposalContext and selects/composes rules into output sections. The skill itself is sound.
• Effort: L overall (the orchestrator), but the skill itself is XS (use as-is).
• Maps to §9.2: Templates (Pyramid maps to template structure), Assembly (orchestration target), ROI, Pricing, Quote (each rule informs a component).

rules/structure-proposal-architecture.md

• What it does today: Defines the winning proposal structure — sections, page budgets, target reader per section.
• Fit: High — defines the Templates scaffold and informs Assembly composition.
• Gaps to close: Encode the structure as machine-readable template metadata so the assembly logic can iterate sections.
• Effort: S.
• Maps to §9.2: Templates, Assembly.

rules/structure-terms-conditions.md

• What it does today: Terms & conditions positioning — when to surface, how to negotiate.
• Fit: Medium — relevant when proposals include T&Cs blocks.
• Gaps to close: Identify which proposals carry T&Cs and template the positioning copy.
• Effort: S.
• Maps to §9.2: Templates.

rules/executive-summary-writing.md

• What it does today: One-page executive summary that compels action in 2-3 minutes.
• Fit: High — the executive summary is a fixed slot in every proposal; the rule encodes the expected content.
• Gaps to close: Bind to a templated section consuming ProposalContext.executive_outcomes.
• Effort: S.
• Maps to §9.2: Templates, Assembly.

rules/executive-stakeholder-alignment.md

• What it does today: Equips the champion with materials to sell the proposal to the buying committee.
• Fit: Medium — informs an optional “internal pitch deck” annex; not a fixed proposal slot.
• Gaps to close: Decide whether the workspace produces a champion-toolkit annex; if yes, template it.
• Effort: S (if scoped in).
• Maps to §9.2: Templates (if annex is in scope), Assembly.

rules/pricing-presentation.md

• What it does today: Pricing anchoring, packaging, “never show price before establishing value”.
• Fit: High — this is the rulebook the pricing configurator must obey when rendering.
• Gaps to close: Encode the rules as a renderer that takes a PricingPlan and outputs the pricing section in compliance.
• Effort: M.
• Maps to §9.2: Pricing, Quote, Templates.

rules/pricing-roi-business-case.md

• What it does today: Business-case framework arming the champion with internal-ROI justification.
• Fit: High — defines the inputs and structure of the ROI calculator output.
• Gaps to close: Encode the framework as input/output schema for the ROI calculator (current state, target state, value drivers, risk-adjusted return).
• Effort: M.
• Maps to §9.2: ROI, Templates, Assembly.

rules/sow-writing.md

• What it does today: SOW scope, deliverables, contractual implementation language.
• Fit: Medium-to-High — SOWs are a common annex to proposals; rule defines structure.
• Gaps to close: Template the SOW with variable scope/deliverable/timeline blocks.
• Effort: S.
• Maps to §9.2: Templates.

rules/rfp-response-strategy.md

• What it does today: RFP/bid response best practice — compliance, win-themes.
• Fit: High — KH already serves UK public-procurement bid writing as a domain; this rule overlaps the existing bid-writing skill but adds proposal-specific framing.
• Gaps to close: Reconcile with KH’s existing bid-writing skill; pick one as canonical or merge.
• Effort: M (reconciliation).
• Maps to §9.2: Templates (RFP-shaped templates), Assembly (RFP-shaped flow).

rules/design-formatting.md

• What it does today: Visual hierarchy, formatting, layout, branding for proposals.
• Fit: High — informs the export pipeline’s styling decisions and the in-workspace preview look-and-feel.
• Gaps to close: Encode as DOCX style decisions inside the export module.
• Effort: M.
• Maps to §9.2: Export, Templates.

rules/strategy-competitive-differentiation.md

• What it does today: Competitive differentiation, positioning vs alternatives.
• Fit: Medium — informs an optional “Why us” section.
• Gaps to close: Template the section with switch-points by competitor archetype; decide whether the workspace surfaces this as a configurable block.
• Effort: S.
• Maps to §9.2: Templates, Assembly.

rules/strategy-followup.md

• What it does today: Follow-up cadence, closing patterns, objection handling, negotiation.
• Fit: Medium — runs after the proposal lands; pairs naturally with draft-outreach from Bucket 2.
• Gaps to close: Wire into a “post-send” workflow; surface follow-up reminders in the workspace.
• Effort: M (workflow + reminders).
• Maps to §9.2: Assembly (post-send).

---

Workflow notes

• The four-bucket structure was easy to scan in parallel because each bucket lives in a distinct subtree; no path conflicts and no need to disambiguate. The exception was the deliberate overlap between starter-kit/skills/proposal-writer/ (Bucket 1) and .claude/skills/proposal-writer/ (Bucket 4) — flagged in §1 to avoid double-counting in §2, then assessed only once in Bucket 4.
• The vendored Anthropic plugin marketplace under starter-kit/plugins/claude-plugins-official/ was opaque at the directory level — the hash-named subfolder (2cd88e7947b7) reads as binary content unless one knows to descend further. Listing all 14 plugin names by ls was sufficient to assess fit; full subtree exploration would have spent a lot of tokens on plugins that are no-fit anyway.
• The proposal-writer rules file naming convention (structure-*, executive-*, pricing-*, sow-*, rfp-*, design-*, strategy-*) is excellent — front-matter impact: and tags: made batch-reading the headers enough to assess fit without reading the full body of each rule. This is exactly the disclosure shape the §9.2 templates component should adopt.
• Frontmatter discipline across the four buckets is uneven: ASIP starter-kit skills mostly have a description: line that doubles as the trigger surface; the local KH skills have richer frontmatter (allowed-tools, argument-hint); the Anthropic sales plugin frontmatter is sparse. Anything reused into KH would benefit from being normalised to the local frontmatter shape during inclusion.
• The mismatch between .claude/skills/proposal-writer/SKILL.md and .claude/plugins/sales/1.1.0/skills/create-an-asset/SKILL.md is interesting: both are “generate a sales artefact” but at different levels of abstraction (strategist’s rulebook vs runtime asset generator). The §9.2 workspace will need both, paired by an assembly orchestrator. Neither is sufficient on its own.