update-project-next-actions
Skill1 starsChanged 19 days agoMITView on GitHub
Reconcile completed, changed and new project next actions in the selected deployed vault; refresh related state when those actions affect it.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ingest-sourceSkill
- lint-vaultSkill
- process-inboxSkill
- process-ready-ingestion-inboxSkill
- review-vault-healthSkill
- start-a-focusSkill
- update-project-summarySkill
- skill.mdSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Read the vault rules, Project Type, and Procedure completely before acting.
- Distinctive: line 22
Keep 3–7 outcome-level actions.
- Distinctive: line 23
Remove completed items, rewrite partial work, and merge overlaps instead of appending duplicates.
- Distinctive: line 26
Add a milestone only for a meaningful state transition and reconcile the human view when needed.
- Distinctive: line 27
Avoid broad cascades, preserve unrelated edits, review the diff, and push only with current explicit authorization.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Project Next Actions
Reconcile what should happen next: remove completed actions, rewrite remaining work and merge overlaps. Refresh related project state when the action changes affect it.
For a broader refresh of current state, scope, blockers and links, use update-project-summary. Both workflows keep actions and state consistent.
Source of truth
- Vault rules:
AGENTS.md - Project contract:
project.md - Complete workflow:
procedures/update-project-next-actions.md
Read the vault rules, Project Type, and Procedure completely before acting.
Guardrails
- Keep 3–7 outcome-level actions; review lists above 10.
- Remove completed items, rewrite partial work, and merge overlaps instead of appending duplicates.
- Route durable uncertainty, knowledge, ownership, workflows, and decisions into the appropriate existing Type only when direct and high-confidence.
- Refresh Project state, questions, links, workflows, or guardrails when action changes affect them.
- Add a milestone only for a meaningful state transition and reconcile the human view when needed.
- Avoid broad cascades, preserve unrelated edits, review the diff, and push only with current explicit authorization.
Select this package by the requested vault role, not its name alone. Reuse rules and the complete Procedure already read in this session while they remain current; reread after a relevant change.
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.