proposal
VerifiedCreate, revise, or audit commercial proposals as editable PowerPoint, interactive HTML, or PDF, with proposal logic, case evidence, scope and pricing, presenter scripts, and format-specific validation. Use for client proposals, pitches, tenders, and proposal revisions, rather than general marketing websites.
references/argument-traceability.md
View on GitHub# Argument traceability
Use while drafting a proposal or repairing a proposal whose strategy feels disconnected. Complement the brief compliance matrix: that checks requirements; this checks why the recommended work follows from the evidence.
## Working map
| Client question | Evidence and source status | Diagnosis / implication | Recommended work | Example or mechanism | Deliverable / acceptance | Timing / dependency | Quote reference |
|---|---|---|---|---|---|---|---|
Use stable internal IDs when a project is large. Keep IDs out of customer-facing headings unless useful. Do not force every introduction or closing page into a paid-service row. Not every problem must be sold a solution: mark deliberately excluded or deferred work and explain why internally.
Check both directions:
- Every important diagnosis has a response, a stated deferral, or a missing-evidence flag.
- Every proposed service has a client need or explicit requirement; remove unmotivated upsells.
- Every case explains what is transferable, not merely who commissioned it.
- Every quoted scope item matches deliverables and schedule; changes propagate to totals, package pricing, appendices and speaker script.
- Do not equate delivery acceptance with revenue, ranking, search inclusion, or other outcomes outside the team's control.
## Example: turn company capability into customer questions
A company says it can produce several model materials. Do not make “材料能力介绍” the entire content strategy. Derive questions customers may actually ask: Which material suits a traveling exhibition? How do size and transport affect the design? What evidence helps compare suppliers?
For each question, record whether it came from interviews, inquiries, search evidence, or is a hypothesis to confirm. Then choose the answer structure and supporting project facts. Do not claim a guessed question has demonstrated demand. For AI-search proposals, explain source preparation and answer usefulness; do not promise that every system retrieves, verifies, or cites every channel.
## Before drawing
For each scene write: “The reader should understand ___, supported/explained by ___, which makes ___ the next relevant decision.” If the evidence is an unrelated screenshot or the next decision does not follow, repair the content first.
Keep the ledger compact and inside project working files. Its purpose is to find gaps, not to add another dense customer-facing table.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |