<< All versions

Skill v1.0.0

currentLLM-judged scan90/100
d-roak/harness/quote-create
──Details
PublishedOctober 22, 2026 at 03:34 PM
Content Hashsha256:a63c7adacedd11a4...
Git SHA7431ceedfe33
──Files
Files (1 file, 3.3 KB)
SKILL.md3.3 KBactive
SKILL.md · 51 lines · 3.3 KB

version: "1.0.0" name: quote-create description: Draft a buyer-ready project quote, proposal or statement of work. Use when scoping, pricing and preparing an engagement for agreement.


quote-create

When

  • A project or engagement needs a formal quote, proposal or statement of work.
  • A verbal estimate needs written scope, pricing and terms.
  • A seller needs to prepare an offer before negotiation.

Steps

  1. Set the engagement. Capture the buyer, problem, engagement type, deadline, budget constraints and intended delivery format. State assumptions when a material fact is absent.
  2. Define delivery. Write inclusions, deliverables, exclusions, buyer dependencies and objective completion conditions. Name required access, decisions, source material, licences and reviewers.
  3. Build the work plan. State the start trigger, delivery sequence, milestones, buyer review windows, dependencies and handover. Label dates as conditional when they depend on buyer action.
  4. Price the work. State the total fixed price or rate, currency and tax treatment. Separate fixed charges, recurring charges and third-party pass-through costs. State change-request treatment and any spend caps.
  5. Set payment and support. Specify invoice dates, due dates, payment schedule, cancellation treatment, warranty, post-delivery support, ongoing operations and the end of any included support period.
  6. Set ownership and governance. State ownership of deliverables, pre-existing materials, data and access. State confidentiality, data retention/deletion where relevant, decision-maker, feedback path, escalation and proposal validity.
  7. Structure for the buyer. Use this order unless an existing format requires another:
  8. Buyer context and problem
  9. Scope and deliverables
  10. Exclusions and dependencies
  11. Work plan and acceptance
  12. Investment, payment and recurring costs
  13. Responsibilities and terms
  14. Next steps and acceptance mechanism
  15. Use the existing presentation system. Reuse the buyer's or seller's approved brand, template and output format when it exists. Without one, deliver a plain, readable outline. Do not manufacture branding.
  16. Self-check. Confirm every material promise has a scope limit, acceptance condition, owner and commercial treatment. List unresolved commercial decisions explicitly.
  17. Verify delivery. Build or render the requested artefact. Check the complete document for missing sections, inconsistent values, unreadable layout and unsupported claims.

Rules

  • Proposal facts only. Never invent capacity, dates, price, legal terms or guarantees.
  • Put exclusions beside inclusions. A buyer must be able to see both without inference.
  • Write buyer obligations with the same precision as seller obligations.
  • A change request has an owner, estimate, approval method and schedule effect.
  • Make “done” measurable. Avoid satisfaction-only acceptance.
  • Treat contract language as business drafting, not legal advice. Recommend qualified review for ownership, liability, privacy, regulatory or jurisdiction terms.
  • Keep output format and branding separate from commercial structure.

Not this skill

  • Buyer-side risk review: quote-eval.
  • Visual design and branding: design, brand.
  • Copy polish: copy.
  • Legal advice or contract drafting.
All versions