ShaneBrain Planning System

Plan and preserve project context across multi-session work using Markdown files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/thebardchat/shanebrain-core --skill shanebrain-planning-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ShaneBrain Planning System
Source: https://github.com/thebardchat/shanebrain-core/tree/main/planning-system
Command: npx skills add https://github.com/thebardchat/shanebrain-core --skill shanebrain-planning-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning across multiple sessions is difficult when interruptions disrupt progress and memory. This Skill provides a persistent, ADHD-friendly planning approach that keeps decisions, context, and progress intact between sessions.

Core Features & Use Cases

  • Visual progress tracking with checkboxes and status indicators across active projects.
  • File-based memory that preserves context via task_plan.md, context.md, errors.md, and decisions.md.
  • Cross-project continuity, enabling seamless switching among Angel Cloud, Pulsar, LogiBot, and ShaneBrain Legacy.

Quick Start

Start by copying a template from templates/ into active-projects/, then fill in task_plan.md and context.md to begin tracking progress with checkboxes.

Frequently Asked Questions about ShaneBrain Planning System

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

FAQPage Schema
How do I preserve project context across multiple sessions using Markdown?

You can preserve project context across multiple sessions by writing decisions and progress into Markdown files like task_plan.md, context.md, and decisions.md, ensuring your work state remains intact after interruptions.

What is the best way to manage cross-project planning for ADHD-friendly workflows?

ADHD-friendly cross-project planning is managed via a dedicated root directory containing templates and an active-projects workspace, using visual checkboxes and status indicators to track progress seamlessly across different projects.

How do I set up a file-based planning system to resume work after an interruption?

Set up a planning-system root with a SKILL.md file, a templates directory, and an active-projects workspace. Copy a template into active-projects and fill in task_plan.md and context.md to start tracking.

Does this project planning approach require any specific dependencies or software?

No specific dependencies or external software are required. The project planning system relies entirely on file-based memory using Markdown files to track context, errors, and decisions within your workspace.

Can I use Markdown files to track progress across multiple active projects?

Yes, you can track progress across multiple active projects using Markdown files. The system supports cross-project continuity, enabling seamless switching between ongoing work by preserving context in structured documents.

When should I archive projects in a file-based planning system?

You should archive projects using an optional completed-projects directory once your work is finished. This keeps the active-projects workspace focused on ongoing tasks while maintaining a historical record of completed work.