Slash Command

/proposal

Scaffold a new OpenSpec change and validate strictly.

Install

Run in your terminal

npx claudepluginhub jbabin91/super-claude --plugin workflow

Details

Namespaceopenspec/

Command Content

Other plugins with /proposal

/proposal

Creates a personalized investment proposal for a prospect by loading the investment-proposal skill. Uses provided prospect name or prompts for details.

wealth-management

7.3k

/proposal

Creates a print-ready multi-page HTML funding proposal with organization branding via guided wizard questions on type, sections, pages, and budget. Accepts optional project-name.

ReadWriteEdit+4

pdf-playground

101

/proposal

Create OpenSpec proposal through collaborative exploration

agentic-skills

/proposal

openspec/

Scaffold a new OpenSpec change and validate strictly.

know

/proposal

Generate a structured sales proposal using the SCRAP framework, then dispatch the proposal-reviewer agent for quality review. Pulls from deal context, company pain points, and relevant case studies.

sales-enablement

/proposal

Generate a project proposal for a client. Scoped, priced, and structured. Activates bb-studio-ops + bb-presentation. Usage: /proposal --client={client} --scope={scope}

brand-bond-os

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitNov 6, 2025

Actions

View Source View Plugin View on GitHub View README

Guardrails

Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
Keep changes tightly scoped to the requested outcome.
Refer to openspec/AGENTS.md (located inside the openspec/ directory—run ls openspec or openspec update if you don't see it) if you need additional OpenSpec conventions or clarifications.
Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.

Steps

Review openspec/project.md, run openspec list and openspec list --specs, and inspect related code or docs (e.g., via rg/ls) to ground the proposal in current behavior; note any gaps that require clarification.
Choose a unique verb-led change-id and scaffold proposal.md, tasks.md, and design.md (when needed) under openspec/changes/<id>/.
Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
Capture architectural reasoning in design.md when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
Draft spec deltas in changes/<id>/specs/<capability>/spec.md (one folder per capability) using ## ADDED|MODIFIED|REMOVED Requirements with at least one #### Scenario: per requirement and cross-reference related capabilities when relevant.
Draft tasks.md as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
Validate with openspec validate <id> --strict and resolve every issue before sharing the proposal.

Reference

Use openspec show <id> --json --deltas-only or openspec show <spec> --type spec to inspect details when validation fails.
Search existing requirements with rg -n "Requirement:|Scenario:" openspec/specs before writing new ones.
Explore the codebase with rg <keyword>, ls, or direct file reads so proposals align with current implementation realities.