mission-tracking
Skill1 starsChanged 5 months agoMITView on GitHub
Use throughout a run to keep the mission file current as the single source of truth.
In this repository6 other files it gives its agents.
- capability-routingSkill
- dispatching-agentsSkill
- reviewing-plansSkill
- verifying-task-outputSkill
- writing-agentsSkill
- writing-plansSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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 11
Write it when the plan is approved (Plan and Tasks sections, all tasks pending).
- Very specific: line 16
Do not narrate state in prose instead of updating the file.
≈ “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.
Files
Mission Tracking
The mission file at .atelier/missions/<date>-<goal-slug>.md is the single source of
truth. Follow the mission schema (docs/schemas/mission-schema.md):
- Write it when the plan is approved (Plan and Tasks sections, all tasks
pending). - Set a task to
in-progresswhen you dispatch it, and todoneorblockedwhen its verification finishes, so the board never shows a running task aspending. - Append routing and ordering decisions to the Decision log.
Do not narrate state in prose instead of updating the file. /status reads this file.
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.

