- Home
- Skills
- Vadimcomanescu
- Codex Skills
- Planning With Files
planning-with-files_skill
- Python
3
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill vadimcomanescu/codex-skills --skill planning-with-files- LICENSE.txt1.1 KB
- SKILL.md882 B
Overview
This skill transforms workflows to use persistent Manus-style markdown files for planning, progress tracking, and knowledge storage. It standardizes how you start complex tasks, record findings, and produce final deliverables using simple file conventions. The approach reduces reliance on ephemeral chat context and creates an auditable project trail.
How this skill works
When enabled, the skill prompts creation of a task plan file (e.g., task_plan.md) before starting any complex or multi-step work. It directs research and raw notes into a separate notes.md, guides you to write deliverables in dedicated output files, and recommends updating the plan file after each phase to record status and errors. Files serve as persistent working memory that the agent reads and writes to keep context across sessions.
When to use it
- Starting a complex or multi-step project that needs tracking and checkpoints
- Conducting research where findings should be stored outside chat for later reference
- Coordinating work that requires repeatable status updates and error logs
- Preparing deliverables that must be drafted, reviewed, and versioned
- When you want an auditable trail of planning decisions and progress
Best practices
- Create task_plan.md before initiating substantive work and list goals, milestones, and owners
- Keep raw findings and source material in notes.md rather than chat to avoid context loss
- Write final outputs in a dedicated deliverable file and link back to the plan
- Update task_plan.md after each phase with status, next steps, and any errors encountered
- Store large data or examples in reference files (e.g., references/examples.md) and cite them in the plan
Example use cases
- Planning a multi-week product feature with milestones, dependencies, and progress logs
- Running a research sprint where literature, experiments, and summaries live in notes.md
- Managing a complex bugfix process with reproducible steps and an error log in the plan file
- Preparing a report: outline in task_plan.md, research in notes.md, and final text in deliverable.md
- Handing off work: the plan file documents decisions and next steps for the incoming contributor
FAQ
Start with task_plan.md for goals and milestones, and notes.md for research and raw findings.
How often should I update the plan file?
Update task_plan.md after each meaningful phase or shift—daily for active sprints, or after each major milestone.