update-current-state
Skill8 starsChanged 11 days agoApache-2.0View on GitHub
Update BRIEFING-CURRENT-STATE.md when work changes project status. Any agent
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/architecture-patterns.mdcCursor rule
- .cursor/rules/completion-discipline.mdCursor rule
- .cursor/rules/github-tracking.mdcCursor rule
- .cursor/rules/programmer-briefing.mdcCursor rule
- .cursor/rules/verification-first.mdcCursor rule
- ab-a-isolationSkill
- assign-sprint-safelySkill
- audit-cascadeSkill
- brief-coding-agentSkill
- check-mailboxSkill
- cleanup-dev-activeSkill
- close-issue-properlySkill
- cohort-attention-rollupSkill
- compost-reviewSkill
- continue-narrativeSkill
- create-omnibusSkill
- create-session-logSkill
- cut-releaseSkill
- delete-module-safelySkill
- deliver-mailSkill
- discovered-work-captureSkill
- doc-sync-sweepSkill
- draft-blog-postSkill
- draft-weekly-shipSkill
- duty-cycle-tickSkill
- narrative-verificationSkill
- piper-draft-issueSkill
- piper-draft-specSkill
- piper-sprint-planSkill
- piper-stakeholder-updateSkill
- piper-synthesize-feedbackSkill
- propose-featureSkill
- publish-to-blogSkill
- query-github-boardSkill
- template-auditSkill
- trust-checkSkill
- update-calendarSkill
- update-piperSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Replace the stale line; don't add one under it: Keep the line's shape: - Item *(Role, YYYY-MM-DD [time], how you know)*: the fact.
- Very specific: line 37
Run python3 scripts/check-current-state.py before committing.
- Distinctive: line 40
Commit and push from your own worktree with the unit of work it describes.
- Distinctive: line 44
Update the lines your evidence covers and leave the rest.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
update-current-state
docs/briefing/BRIEFING-CURRENT-STATE.md is a short "Now" page (v2.0, 2026-10-08, R6 step 3,
PM-approved 2026-10-04). It says where the project stands today, one dated line per item. It is no longer
a progress log: the old 169 KB file, Recent Progress included, is verbatim in
docs/internal/architecture/decisions/briefing-current-state-history.log, and day-by-day progress lives
in the omnibus logs.
When to use
- Your work changed something the Now page states: the live alpha version, the latest tag, the MVP count, engineering focus, a usage or mail change, the R6 status, or a milestone position.
- The session-start hook says
BRIEFING: STALE, or a line you can attest to is visibly wrong (PM's standing request, 2026-04-22: any agent refreshes it; a partial update beats none).
How
- Get the fact from its source this turn, not from memory:
curl https://piper-morgan.fly.dev/health,git tag,python3 scripts/sprint-truth.py, the rollup, your own session log. - Replace the stale line; don't add one under it. Keep the line's shape:
- **Item** *(Role, YYYY-MM-DD [time], how you know)*: the fact. - Bump front-matter
last_updated(andlast_verified) to the newest date on the page. - Narrative goes elsewhere: what happened belongs in your session log (the omnibus picks it up); superseded context worth keeping goes to the history log, appended, never into this page.
- Run
python3 scripts/check-current-state.pybefore committing. CI runs it too (Code Quality): it fails if the page exceeds itssize_cap_bytes(12,000) or iflast_updatedis older than the newest attested line. - Commit and push from your own worktree with the unit of work it describes.
Only attest what you can
Update the lines your evidence covers and leave the rest. If you notice a line is wrong but can't verify the right value, say so in the line ("stale per X; owner to correct") rather than guessing.
Anti-patterns
| Don't | Instead |
Append an "UPDATE <dates>" paragraph | Overwrite the line with today's fact and source |
| Copy PM's open-asks list onto the page | Link the attention rollup |
| Paste sprint lists | Point to sprint-truth.py |
Leave last_updated behind the newest line | Bump it; CI enforces this |
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
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.

