planning-with-files

Creates file-based task plans anchored to real repository paths and tools.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Martino17x/Sentinel-Invest --skill planning-with-files-martino17x
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-with-files
Source: https://github.com/Martino17x/Sentinel-Invest/tree/main/.agents/skills/planning-with-files
Command: npx skills add https://github.com/Martino17x/Sentinel-Invest --skill planning-with-files-martino17x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Long agent sessions lose track of goals after many tool calls, and abstract plans drift away from the actual repository structure. This Skill keeps plans short, verifiable, and grounded in real files by persisting goals, decisions, and progress to Markdown files on disk. ## Core Features & Use Cases - File-anchored minimal planning: Produces plans of at most 3 steps tied to concrete paths, symbols, and the cheapest discovery tool (list_files, search_files, read_file). - Persistent planning files: Ships templates for task_plan.md, findings.md, and progress.md plus init scripts (Bash/PowerShell) to bootstrap a session. - Completion and catch-up automation: check-complete scripts verify all phases are done, and session-catchup.py detects unsynced context from previous sessions. - Use Case: Before editing code, ask the agent to plan the next change; it returns an entry point file, an initial tool, a 3-step plan, and a closure criterion instead of a long abstract strategy. ## Quick Start Ask the agent to plan the next concrete step for your task using real repository files and tools before making any edits.

Frequently Asked Questions about planning-with-files

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep an AI agent on track during long tasks?▼

Write goals, phases, and decisions to persistent Markdown files like task_plan.md and re-read them before major decisions. This refreshes the goal in the model's attention window after many tool calls.

How do I plan code changes without over-exploring a repository?▼

Anchor the plan to one known file, symbol, or search, pick the cheapest discovery tool first, and limit the plan to at most three verifiable steps. Avoid opening files just to gather context.

What files does this planning workflow create?▼

It creates task_plan.md for phase tracking, findings.md for discoveries and decisions, and progress.md for session logs. The init-session scripts generate all three from templates.

How do I verify all task phases are complete?▼

Run the check-complete.sh or check-complete.ps1 script against task_plan.md. It counts phases by status and exits with code 0 only when every phase is marked complete.

When should I not use file-based minimal planning?▼

Avoid it when base context is still missing and a broad strategy is needed; recover context or read surgically first. It is designed for converting known goals into concrete file-level steps, not open-ended exploration.