procedure-playbooks
Skill2 starsChanged 34 days agoMITView on GitHub
Ingests and surfaces procedure playbooks as knowledge for planning (explicit CLI)
In this repository52 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/00-core-operating-model.mdcCursor rule
- .cursor/rules/01-plan-approval-gate.mdcCursor rule
- .cursor/rules/02-git-worktree-policy.mdcCursor rule
- .cursor/rules/03-validation-definition-of-done.mdcCursor rule
- .cursor/rules/04-documentation-memory.mdcCursor rule
- accessibility-reviewSkill
- agent-skills-packagingSkill
- autonomy-budgetSkill
- bounded-autonomySkill
- candidate-promotionSkill
- capability-planningSkill
- code-reviewerSkill
- code-structure-cleanupSkill
- compass-evaluatorSkill
- context-inodesSkill
- dependency-supply-chainSkill
- docker-cloudSkill
- embedding-providersSkill
- execution-telemetrySkill
- experience-routingSkill
- experience-skill-trainingSkill
- external-knowledge-ingestSkill
- github-integrationSkill
- goose-agent-orchestrationSkill
- harness-gcSkill
- hosted-vector-dbSkill
- implementation-planningSkill
- ios-engineeringSkill
- knowledge-stewardSkill
- linear-integrationSkill
- node-engineeringSkill
- northstar-connected-routineSkill
- notion-integrationSkill
- package-registry-tiSkill
- persistent-role-promotionSkill
- playwright-browser-validationSkill
- postgres-prismaSkill
- project-overseerSkill
- pull-request-preparationSkill
- python-mlSkill
- react-engineeringSkill
- repository-discoverySkill
- review-fix-loopSkill
- security-audit-proceduresSkill
- security-reviewSkill
- skill-learning-loopSkill
- skill-lifecycleSkill
- source-code-contextSkill
- technology-intelligence-liveSkill
- testing-validationSkill
- worktree-orchestrationSkill
The file
Files
Procedure Playbooks
Use this Skill when
The Captain or First Mate needs reusable procedure playbooks surfaced during planning — validated sequences from staging or approved procedure roots.
Prerequisites
- Playbooks under
.agent/knowledge/procedures/staging/or.../approved/ - Optional prior step:
propose-procedure-from-knowledge.sh(staging only)
Procedure
Propose (optional — creates staging draft, does not ingest):
./scripts/propose-procedure-from-knowledge.sh \ --item-ids know-adr-020 \ --title "Bounded weight apply playbook"Ingest procedure playbooks (explicit CLI only):
./scripts/ingest-knowledge.sh --from-store proceduresIngests
playbook.mdfrom staging and approved roots. Re-ingest overwrites existingknow-proc-*items idempotently.Query for readback:
./scripts/query-knowledge.sh --query "bounded autonomy apply" --kind procedure- Review Procedure Context in capability plans (always rendered; empty when none).
- Land approved playbooks via Captain-reviewed PR — never auto-install into Skills.
Output
- Knowledge items
kind: procedureunder.agent/knowledge/items/ - Plan section Procedure Context (informational only)
Prohibited actions
- Auto-ingest on procedure proposal write
- Silent install of playbooks into
.cursor/skills/or rules - Mutating matcher weights from procedure readback
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.