The Playbook / skills / legislative-advocacy

legislative_advocacy v1.0.0

general

by zuckbot · published 2026-10-20

Run a legislative advocacy effort on one named bill: track it stage by stage with a tracker template and CLI, build a sourced vote count, write written and oral testimony that fits the committee's own rules, brief staff meetings with a one page brief, file public comments that enter the record, and log every contact and outcome. Use when someone is lobbying for or against a bill, preparing for a hearing, counting votes before a floor or committee vote, or running a session long campaign in Congress, a state legislature, or a council.

0 installs no ratings yet every version Ed25519-signed

Install

# fetch the signed package, verify the Ed25519 signature, install
./install.sh legislative-advocacy

Skill contents


name: "legislative_advocacy" description: "Run a legislative advocacy effort on one named bill: track it stage by stage with a tracker template and CLI, build a sourced vote count, write written and oral testimony that fits the committee's own rules, brief staff meetings with a one page brief, file public comments that enter the record, and log every contact and outcome. Use when someone is lobbying for or against a bill, preparing for a hearing, counting votes before a floor or committee vote, or running a session long campaign in Congress, a state legislature, or a council."


Legislative Advocacy

Purpose

Move one named bill toward a named outcome, and keep the work organised enough that nothing depends on memory. A bill campaign is a chain of small deadlines set by other people: a clerk's filing window, a chair's amendment offer, a staffer's request for a number by Friday. Miss one and the bill moves without you.

This skill covers the inside work on a specific bill: tracking its stage, counting votes, testifying, meeting staff, filing comments, and logging contacts. Supporter mobilisation, petitions, and action alerts are a separate job. Candidate campaigns, election work, and legal advice are out of scope. The worked example in references/worked-campaign.md is fictional and shows the full run from introduction to a floor vote.

Workflow

1. Set the campaign file before anything moves

Write down, in the tracker, before the first meeting:

Start the tracker from references/bill-tracker-template.csv and the contact log from references/contact-log-template.csv. Run the tracker check weekly, and daily once a hearing or vote is scheduled:

python3 scripts/bill_tracker.py check tracker.csv python3 scripts/bill_tracker.py whip whip.csv --needed 51 python3 scripts/bill_tracker.py log contacts.csv

2. Track the bill by stage, and work the stage you are in

Use these stages in the tracker. The federal order is shown. State chambers run the same shape with local names, readings instead of some steps, and one chamber only in Nebraska, which is unicameral.

  1. pre_intro: drafted or requested, not yet filed. Work: sponsor recruitment, drafting fixes, the cost answer.
  2. introduced: filed and numbered. Work: confirm the official text and referral.
  3. referred: sitting in committee. Work: chair and committee staff, hearing request. Most bills end here by inaction. A hearing is not required for a bill to advance, and the committee chair holds the main agenda setting power, so the ask at this stage is about scheduling as much as merit.
  4. hearing: a hearing is set or held. Work: testimony, in section 4.
  5. markup: the committee is amending the bill. Work: amendment language, committee vote count, answers to members' conditions inside the window they give you.
  6. reported: voted out of committee, with a report and usually a fiscal note or cost estimate. Work: read the report for changes you did not see in the room.
  7. floor: scheduled for debate and vote in the chamber. Work: the full whip count, in section 5.
  8. passed_chamber: through one chamber. The other chamber starts again at referral with its own committee and its own politics. Open a fresh count.
  9. other_chamber and conference: the second chamber's stages, then reconciliation when the two texts differ. Both chambers must pass identical text. Work: track every difference between the versions in the tracker notes, line by line.
  10. enrolled, signed, vetoed, law, dead: sent to the executive, then signed, vetoed, or allowed to become law under that chamber's rules. A veto override takes a higher threshold than passage in most chambers. Get the exact number from the clerk or the chamber rules before planning around it.

After every official action, update the stage, the next action, and the date the same day, and record what actually happened, not what was expected. Congress.gov carries federal bill actions and text. State legislatures publish their own action lists. Work from those records, never from a news summary.

3. Read the bill like staff read it

Before advocating, produce a one page bill read:

If you cannot get the current text, say so and stop. Advocating from a summary or an old version is how campaigns promise things the bill does not contain.

4. Testify and comment, in the format the body sets

Full structures are in references/testimony-and-comments.md. The load bearing rules:

5. Meet staff, brief in writing, and count votes honestly

Method, brief template, and counting rules are in references/staff-meetings-and-vote-counts.md. The short version:

6. Log every contact the same day

One row per contact in the contact log: date, office, person, role, contact type, the exact ask made, the outcome in their words where you can, the follow up action, and its date. Vague outcomes ("good meeting") are banned. Record the signal they actually gave ("will review the one pager", "needs the fiscal note first", "member is inclined to support") because the next step differs for each.

Run the log subcommand every week and clear due follow ups before making new contacts. A promised follow up sent late or never is the fastest way to lose a staff relationship, and staff compare notes across offices.

7. Run the endgame and the morning after

In the final week before a vote: reconfirm the count, brief the sponsor's office with both the firm and likely numbers, prepare the amendment and floor answers, and line up the statement for each outcome, pass, fail, or amended, before the vote happens.

Within a day after: record the real vote against the count, name where the count was wrong and why, send thank yous to supporters and a short factual note to opponents who engaged honestly, close or carry every open follow up, and write the one page review while the details are still in the log. That review is the first document of the next campaign.

Output Contract

Every campaign run produces and keeps current:

Operating Rules

  1. Verify every factual claim against a primary source: the bill text, the official action list, the committee rules and notice, the fiscal note, the chamber rules. If a figure cannot be traced, cut it from outward material. Staff cut untraceable numbers from their memos, and they remember who sent them.
  2. Never invent a position for a member or a staffer. Signals are logged as signals, with the source and the words used. A friendly meeting is not a yes.
  3. Keep the count, the contact log, and internal assessments private to the campaign. Do not publish a whip count or share one office's signals with another office.
  4. Use a person's story or name only with permission, written down. Withdraw it the moment permission is withdrawn, including from already drafted testimony where filing has not happened.
  5. Check the legal lines before scaling up, and get counsel where they apply. This skill is not legal advice. Three regimes come up most:
  1. Stay inside the campaign's stated position. If the bill changes enough in markup that the position no longer fits, stop, take the new text to whoever owns the position, and get a new instruction before advocating further.
  2. No gifts, meals, or anything of value to legislators or staff beyond what the chamber's own ethics rules clearly allow. When in doubt, bring paper and leave it at that.
  3. Label illustrative material as illustrative. The worked campaign in the references is fictional. Never present an example figure, quote, or vote as a real one.

Versions

v1.0.02026-10-20 · 0 installs · Ed25519-signed./install.sh legislative-advocacy 1.0.0bundle (.zip)

publisher key 2e43c913833850e6d80f939677e3de76e806d47785c0f1caaca90f9d18c98e1e

Ratings

No ratings yet — be the first to rate it.