planning

Planning

Persistence

This skill belongs to the plans skill group. A persistence implementation decides where and how plans are stored. Before creating or updating a plan, find the setting:

R="$(git rev-parse --show-toplevel 2>/dev/null)/.ai/config.properties"; { cat "$R" ~/.ai/config.properties | grep '^persistence\.plans[[:space:]]*=[[:space:]]*[^[:space:]]'; cat "$R" ~/.ai/config.properties | grep '^persistence[[:space:]]*=[[:space:]]*[^[:space:]]'; } 2>/dev/null | head -1 | tr -d ' \t\r'

• No output: use local-ai-folder-markdown, the default for this skill group
• persistence.plans={value} or persistence={value}: use {value}. If ./persistence/{value}.md does not exist, tell the user the plans skill group has no {value} implementation and use local-ai-folder-markdown

Read ./persistence/{implementation}.md and follow it whenever this skill creates a plan or reads, writes or updates a planning document.

Every plan is identified by:

• {yyyy-mm-dd}, the date of the plan creation
• {task-name}, an extremely succinct name for the task in kebab-case

Planning documents

Use persistent planning documents as your working memory. Context windows are volatile and limited; anything important gets persisted.

• For any plan, you must create the following documents in the plan:
  • plan — Track work breakdown and progress
  • questions — Track your questions and the user's responses and vice versa
  • findings — Store research and discoveries
• For multi-phase plans, you must also create:
  • progress — Session log and test results
• Before creating the planning documents, you must read the starting templates in ./templates/
• You must use the starting templates when creating or updating planning documents to guide their structure and content. Write the content in Markdown; the persistence implementation decides how it is stored

Document	Template	Purpose	When to Update	Scope
plan	plan.md	Work breakdown, decisions	After each phase	All plans
findings	findings.md	Research, discoveries	Per 2-action rule	All plans
questions	questions.md	Log of questions and user responses	Throughout planning	All plans
progress	progress.md	Session log, test results	Throughout session	Multi-phase only