SkillVaultskills Browse all 500 skills

Writing · Version 1.0.0 · Reviewed 2026-08-02

Proposal Compliance and Traceability Editor

Make the reader act on requirement coverage check and claim evidence review with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 5 diagnostic checks 7 quality gates

Reviews a proposal against explicit customer requirements and ensures every claim, section, attachment, owner, and evidence reference is present and traceable.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Requirement coverage check
  • Claim evidence review
  • Submission readiness

How Proposal Compliance and Traceability Editor works

You provide

Obligations, data inventory, and current controls

It inspects

Requirement type and implemented control for requirement coverage check

It decides

A claim evidence review gap register with accountable owners

You verify

Each control mapped to evidence an auditor would accept

What it checks first

Proposal Compliance and Traceability Editor reviews a proposal against explicit customer requirements and ensures every claim, section, attachment, owner, and evidence reference is present and traceable. Use it when the work involves Requirement coverage check, Claim evidence review, Submission readiness.

  1. Whether the obligation is a legal requirement, a contractual commitment, or an internal policy — the escalation path differs.
  2. The specific data categories and lawful basis, rather than a general statement about compliance.
  3. Data flows across jurisdictions and processors, which determine transfer obligations.
  4. Retention and deletion behavior in every downstream copy, including backups and analytics.
  5. Who is accountable for the decision, since a compliance analysis without an owner is not actionable.

Failure modes it recognizes

  • Deletion implemented in the primary store while copies persist in backups, exports, logs, and warehouses.
  • Consent collected for one purpose and reused for another without a valid basis.
  • A subprocessor added without a data-processing agreement or customer notification.
  • Retention policy defined but never enforced by an automated job.
  • A control documented in policy but not implemented in the system it describes.

Answers it will reject

  • Providing a definitive legal conclusion rather than a structured analysis for qualified review.
  • Treating a compliance certification as evidence that a specific control works.
  • Relying on contractual language to mitigate a technical risk that is technically preventable.
  • Presenting risk without severity, likelihood, and the accountable owner.

Decision rules it applies

  • Separate legal requirement, contractual obligation, and internal policy in every finding.
  • Escalate to qualified counsel for anything that constitutes legal advice, and say so plainly.
  • Map every obligation to a specific implemented control and its evidence, or mark it as a gap.
  • Prefer technical enforcement over documented intent, because documented intent is not a control.

Evidence it asks for

  • Build a data inventory: category, source, purpose, basis, location, retention, and downstream copies.
  • Trace one deletion request end to end and enumerate every store it must reach.
  • Record the evidence artifact that would satisfy an auditor for each control.

The method inside

  1. Identify the reader decision before drafting
  2. Lead with the conclusion and strongest evidence
  3. Remove unsupported claims and background that does not change action
  4. Check traceability, ambiguity, and the explicit ask

Deliverables

  • Requirement coverage check revised draft
  • Claim evidence review source and logic check
  • Submission readiness approval-ready version

Evidence requirements

  • Source analysis, facts, decisions, and approved claims
  • Named audience, decision, and desired action
  • Format, length, tone, and review constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Check this proposal against the customer’s submission instructions and compliance matrix before final approval.

Expected output

Three mandatory requirements are only implied, the implementation timeline conflicts with the pricing appendix, and one customer claim has no approved evidence...

Boundaries and compatibility

Ideal for

  • Requirement coverage check: produce a decision or artifact grounded in supplied evidence.
  • Claim evidence review: produce a decision or artifact grounded in supplied evidence.
  • Submission readiness: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Inventing facts, quotations, or approvals
  • Hiding uncertainty or material bad news

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.