agentleFS
chakmarebelchakmarebel/federal-proposal-copilot/.claude/skills/capture-scorecard/SKILL.md

capture-scorecard

Skill4 starsChanged 3 months agoMITView on GitHub

Use this skill to assess capture readiness across 9 dimensions before committing proposal resources. Produces a stoplight scorecard (Red/Yellow/Green), identifies the top risks, and gives a go/no-go recommendation. Reads from working/ files and writes to working/capture-scorecard.md.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After /proposal-manager completes (proposal plan exists)

    line 17
  2. Very specific:

    After /competitor-assessment completes (competitive picture exists)

    line 18
  3. Very specific:

    Before committing to full proposal effort (before /proposal-writer begins)

    line 19
  4. Distinctive:

    Do we have a credible, differentiated technical solution?

    line 64
  5. Distinctive:

    Do we understand the competitive landscape and have a strategy to win?

    line 90
  6. Distinctive:

    Do we have a pricing strategy and know the competitive price range?

    line 103
  7. Distinctive:

    Ask: Do we know the customer's budget?

    line 111
  8. Distinctive:

    Do we have the people and budget to write a competitive proposal?

    line 142
  9. Distinctive:

    After assessing all 9 dimensions, produce the scorecard:

    line 156
  10. Distinctive:

    If the user cannot answer a question, that dimension defaults to Yellow (unknown = risk)

    line 221
  11. Distinctive:

    Do not let an overall strong capture position mask a single Red in a blocking dimension

    line 222

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Capture Scorecard Skill

Purpose

A fast, honest self-assessment of where you stand on a pursuit before committing B&P dollars to full proposal development. The scorecard takes 10–15 minutes, surfaces hidden risks, and either validates the go decision or forces a conversation about gaps that need fixing first.

A proposal written from a weak capture position loses. This skill tells you whether you're ready to write.

When to Use

  • After /proposal-manager completes (proposal plan exists)
  • After /competitor-assessment completes (competitive picture exists)
  • Before committing to full proposal effort (before /proposal-writer begins)
  • On recompetes: run at 12+ months before recompete due date
  • Any time capture leadership wants a status snapshot

Inputs

Read before scoring:

  1. working/proposal-plan.md — opportunity classification, prime/sub decision, evaluation criteria, win themes, bid/no-bid assessment
  2. working/competitor-assessment.md — competitive landscape, teaming gaps
  3. working/customer-profile.md — customer relationship status, hot buttons
  4. inputs/02_yourCompany/ — your company's capabilities and past performance
  5. inputs/06_notes/ — any meeting notes or relationship intel

For each dimension where information is missing, ask the user to fill it in before scoring. Do not score blindly — a missing answer is itself a yellow or red flag.


The 9 Dimensions

1. Management (MGMT)

Is the capture organized and led?

ScoreCriteria
🟢 GreenCapture manager assigned; capture plan documented; team roles defined; regular reviews scheduled
🟡 YellowCapture manager assigned but plan incomplete or team not fully assembled
🔴 RedNo capture manager; no plan; no organized team

Ask: Who is leading this capture? Is a capture plan in place? Is the team assembled?


2. Shaping

Have we influenced the requirements before the solicitation drops?

ScoreCriteria
🟢 GreenWe have had substantive conversations with the customer about requirements; our solution approach is reflected in the draft/final solicitation; we have a champion inside the program
🟡 YellowSome customer access; limited shaping; RFP language somewhat favorable
🔴 RedNo customer access; requirements were written without our input; we are seeing this cold

Ask: Have we briefed our solution to the customer? Have we seen draft requirements? Do we have a champion?


3. Technical / Solution

Do we have a credible, differentiated technical solution?

ScoreCriteria
🟢 GreenSolution design is mature; capability matrix complete with no mandatory gaps; discriminators identified; solution aligns to evaluation criteria
🟡 YellowSolution approach defined but gaps exist; some requirements not fully addressed; discriminators weak
🔴 RedNo solution design; major capability gaps; cannot address key requirements without significant gaps or unproven assumptions

Ask: Is the capability matrix complete? Are there mandatory requirements we cannot address? What are our discriminators?


4. Teaming

Is the team assembled to fill all capability gaps?

ScoreCriteria
🟢 GreenAll mandatory capability gaps filled by identified partners; teaming agreements in progress or signed; work share defined; no OCI risks
🟡 YellowKey partners identified but not locked; teaming agreements not started; some gaps remain
🔴 RedMandatory gaps with no partner identified; teaming strategy undefined; OCI risk unresolved

Ask: What capability gaps exist? Have partners been identified and approached? Are teaming agreements in progress?


5. Competition

Do we understand the competitive landscape and have a strategy to win?

ScoreCriteria
🟢 GreenTop competitors identified with profiles; Bidder Comparison Chart or competitive landscape complete; strategy statements developed; incumbent assessed
🟡 YellowKey competitors known but limited intelligence; no formal competitive strategy
🔴 RedCompetition unknown; incumbent not assessed; no competitive strategy

Ask: Who are the top 2-3 competitors? Is there an incumbent? Do we have a competitive strategy?


6. Finance / Pricing

Do we have a pricing strategy and know the competitive price range?

ScoreCriteria
🟢 GreenPTW estimate complete; customer budget known or estimated; pricing strategy defined (LPTA vs. best value); fee and margin approach set
🟡 YellowROM pricing only; customer budget unknown; limited PTW intelligence
🔴 RedNo pricing strategy; no estimate; budget unknown; not prepared to price competitively

Ask: Do we know the customer's budget? Do we have a PTW estimate? What is our pricing strategy?


7. Marketing / Positioning

Does the customer know who we are and associate us with this capability?

ScoreCriteria
🟢 GreenWe have previously briefed or demonstrated our solution to this customer; they associate [Your Company] with this capability area; our brand is established with this program office
🟡 YellowSome customer awareness; one prior engagement; limited prior demonstrations
🔴 RedCustomer does not know [Your Company]; no prior demonstrations or briefings; starting from zero

Ask: Have we ever briefed this customer on our capabilities? Do they know our name?


8. Customer Engagement

What is the quality of our relationship with the decision-making chain?

ScoreCriteria
🟢 GreenRegular access to the program manager, technical lead, or end users; champion identified inside the program; customer issues and hot buttons well understood from direct conversations
🟡 YellowOccasional access; relationship is transactional; limited insight into internal priorities
🔴 RedNo access to key decision makers; customer engagement not established; issues inferred, not validated

Ask: Who do we know in the program office? When did we last engage? Do we have a champion?


9. Resources

Do we have the people and budget to write a competitive proposal?

ScoreCriteria
🟢 GreenProposal team identified and available during the proposal period; B&P budget allocated; subject matter experts committed; no competing proposal conflicts
🟡 YellowKey personnel identified but availability uncertain; B&P budget not formally allocated; some schedule conflict risks
🔴 RedNo proposal team; no B&P budget; key personnel unavailable; competing proposal conflicts

Ask: Who will write this proposal? Are they available? Is B&P budget approved?


Scoring and Recommendation

After assessing all 9 dimensions, produce the scorecard:

# Capture Scorecard — [Proposal Name]
**Date:** [today]
**Capture Mode:** [Full Capture / Responsive]
**Prime vs. Sub:** [PRIME / SUB / CO-PRIME]

| # | Dimension | Status | Key Issue | Recommended Action |
|---|-----------|--------|-----------|-------------------|
| 1 | Management | 🟢/🟡/🔴 | | |
| 2 | Shaping | 🟢/🟡/🔴 | | |
| 3 | Technical / Solution | 🟢/🟡/🔴 | | |
| 4 | Teaming | 🟢/🟡/🔴 | | |
| 5 | Competition | 🟢/🟡/🔴 | | |
| 6 | Finance / Pricing | 🟢/🟡/🔴 | | |
| 7 | Marketing / Positioning | 🟢/🟡/🔴 | | |
| 8 | Customer Engagement | 🟢/🟡/🔴 | | |
| 9 | Resources | 🟢/🟡/🔴 | | |

**Score:** X Green / X Yellow / X Red

## Overall Readiness Assessment
[One paragraph: what's strong, what's at risk, what must be resolved before proposal kickoff]

## Go / No-Go Recommendation
**[GO / NO-GO / GO WITH CONDITIONS]**

[Rationale — 2-3 sentences]

## Conditions (if conditional go)
1. [Condition that must be resolved before proposal kickoff]
2.
3.

## Top 3 Actions Before Proposal Kickoff
1. [Most urgent — owner and deadline]
2.
3.

Threshold guidance:

  • 7–9 Green → GO
  • 5–6 Green, remainder Yellow → GO WITH CONDITIONS (state them)
  • Any Red in dimensions 3, 4, or 9 (Technical, Teaming, Resources) → NO-GO until resolved — these are execution risks, not just competitive risks
  • Any Red in dimensions 2 or 8 (Shaping, Customer Engagement) on a competitive RFP → serious concern; flag prominently

Output File

Always write to working/capture-scorecard.md — do not just display in chat.


After Running This Skill

Tell the user:

  1. Overall score (X Green / X Yellow / X Red)
  2. Go / No-Go recommendation with one-sentence rationale
  3. Top 3 actions to take before proposal kickoff
  4. Any dimension scored Red that represents a bid-blocking risk

Rules

  • Score based on what is known, not what is planned — a plan to do something is not the same as having done it
  • If the user cannot answer a question, that dimension defaults to Yellow (unknown = risk)
  • Do not let an overall strong capture position mask a single Red in a blocking dimension
  • Re-run this scorecard after major capture events (customer meeting, solicitation release, teaming agreement signed) to update the picture

Lessons Learned

On Shaping

The biggest recurring gap for small companies is Shaping. Most bids are reactive — solicitation drops, we respond. Proactive shaping (briefing before the RFP, influencing requirements language) dramatically increases win probability. Even a single pre-solicitation meeting that results in favorable language is worth more than weeks of proposal writing. Target Shaping as a consistent Yellow-to-Green improvement area.

On Customer Engagement

For SOCOM and SOF-adjacent customers, end-user operator relationships are more valuable than program office relationships. An operator who has used your solution and will say so to the PM is a stronger signal than a formal meeting with the contracting officer. Track operator relationships as part of Customer Engagement.

On Resources for Responsive Bids

For SBIR/CSO/OTA, the "Resources" bar is lower — a 1-2 person writing effort for a 10-page white paper is sufficient. Don't penalize a responsive bid for lacking a full proposal team. Scale the resource standard to the proposal complexity.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.