Store task plans, milestones, and blockers in Markdown files.
npx skills add https://github.com/42atom/msgcode --skill plan-files
Please help me install this Agent Skill. Skill: plan-files Source: https://github.com/42atom/msgcode/tree/main/src/skills/runtime/plan-files Command: npx skills add https://github.com/42atom/msgcode --skill plan-files
This skill is used when tasks are complex enough to benefit from task-local planning files, but should not introduce a new plan mode, supervisor, or memory layer.
Create a single plan markdown file outlining the task goals, phases, acceptance criteria, and evidence.
High-intent search queries and answers about installing and using this skill.
Task planning can be tracked using on-disk Markdown files to store milestones and evidence, keeping context lean without introducing a new memory layer or supervisor mode.
File-first planning stores task goals, phases, and acceptance criteria in local Markdown files, keeping planning memory out of the active workspace while reusing existing repository protocols.
Create a single Markdown planning file outlining task goals, phases, acceptance criteria, and evidence to establish clear boundaries between plan, memory, and the task workflow.
Use local planning files when tasks span multiple files or modules and require structured progress tracking, but do not warrant introducing a new plan mode or memory layer.
Yes, file-first planning leverages current repository conventions and protocols instead of inventing a new planning platform, ensuring structured progress tracking fits existing workflows.
ReScienceLabCreate an isolated git worktree for a feature branch with automatic project setup.
ITSaltReview completed tasks against BE, FE, or TECH checklists and produce a review artifact.
EmasoftCapture and synchronize task progress, dependencies, and recovery notes for per-team AMCOS contexts.
GamezarDesign multi-agent architectures with supervisor, peer-to-peer, and hierarchical patterns.
