$ loading_
Manage complex work with persistent Markdown plans tracking goals, progress, and decisions.
This skill appears to be an open-source, MIT-licensed prompt-only skill with no required secrets and no declared remote endpoints, indicating low overall risk from the available materials. Although it mentions 'with-files' and 'persistent markdown planning,' the current evidence shows no standalone code execution, data exfiltration, or excessive-permission red flags.
The materials explicitly state that no keys or environment variables are required, and there is no request for API keys, tokens, or other sensitive credentials, so credential exposure and abuse risk appears low.
No remote endpoints are declared, and the system flags it as prompt-only; based on the available materials, there is no evidence of user data being sent to external services or unknown hosts.
The available materials do not indicate that it launches local processes, runs scripts, or invokes system-level capabilities; as a prompt-only skill, it does not itself demonstrate standalone code execution privileges.
The description mentions 'persistent markdown planning' and the name includes 'with-files,' but the system classifies it as prompt-only and there is no README detailing read/write scope; therefore, the materials alone do not show independent or excessive data-access permissions.
The source is an open GitHub repository under the MIT license, which provides good auditability, and its strong community adoption (~22.8k stars) is a meaningful risk-reducing signal. Unknown maintenance status is a minor information gap, but not a high-risk red flag.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "planning-with-files" yet — see the docs or source repo.
Create a persistent Markdown plan for “refactoring the user permission system,” including goals, milestones, risks, a task checklist, and a daily progress update format.
A structured Markdown planning document for ongoing task breakdown, progress tracking, and key decisions.
Help me plan a “new feature release” in a Manus-style workflow and output a Markdown file with phases, owners, dependencies, acceptance criteria, and status fields.
A collaborative, maintainable release plan that helps the team execute and review consistently.
Turn a “competitive research project” into a persistently updated Markdown plan with research questions, sources, findings, next actions, and a decision log.
A Markdown workspace for long-term research tracking that captures both process and conclusions.
Plan projects in Claude, track progress, and resume work with full context.
Consolidate scattered project markdown into one canonical CLAUDE.md with pinned progress.
Read and analyze project schedule files to answer task and progress questions.
Maintain implementation plans and handoff notes as Markdown in your project folder.
Create objective-driven plans for agent-led development with an audit trail.
Manage Microsoft Planner plans, buckets, and tasks through Microsoft Graph.