nessar
bb8d09dda4
- Created SKILL.md and SKILL-MECHANICS.md for writing agent skills. - Added openai.yaml for agent interface configuration. - Introduced AGENTS.md for agent skills overview. - Established CONTEXT.md for personal leave planning terminology. - Documented ordered heuristic optimization in ADRs. - Defined personal client-side planner limitations in ADRs. - Created domain documentation for engineering skills. - Added issue tracker guidelines for GitLab. - Mapped triage labels for issue tracking. - Initialized skills-lock.json to manage skill dependencies.
32 lines
1.5 KiB
Markdown
32 lines
1.5 KiB
Markdown
# MISSION.md Format
|
|
|
|
`MISSION.md` lives at the workspace root. It captures the _reason_ the user is learning this topic. Every teaching decision — what to teach next, which resources to surface, which exercises to design — should trace back to this document.
|
|
|
|
## Template
|
|
|
|
```md
|
|
# Mission: {Topic}
|
|
|
|
## Why
|
|
{1-3 sentences. The concrete real-world goal the user is chasing. What changes in their life or work when they have this skill? Avoid abstract framings like "to understand X" — push for the underlying outcome.}
|
|
|
|
## Success looks like
|
|
- {A specific, observable thing the user will be able to do}
|
|
- {Another specific thing}
|
|
- {…}
|
|
|
|
## Constraints
|
|
- {Time, budget, prior commitments, learning preferences, anything that bounds the approach}
|
|
|
|
## Out of scope
|
|
- {Adjacent topics the user explicitly does not want to chase right now — protects the zone of proximal development}
|
|
```
|
|
|
|
## Rules
|
|
|
|
- **One mission per workspace.** If the user wants to learn two unrelated things, that is two workspaces.
|
|
- **Concrete over abstract.** "Run a half marathon by October" beats "get fitter." "Ship a Rust CLI to my team" beats "learn Rust."
|
|
- **Push back on vagueness.** If the user cannot articulate why, interview them before writing anything. A bad mission is worse than no mission.
|
|
- **Revise when reality shifts.** Missions change. When the user's goal moves, update this file — don't leave a stale mission steering future sessions.
|
|
- **Keep it short.** If `MISSION.md` runs past a screen, it has stopped being a compass and started being a plan.
|