persistent-planning
Persistent planning system with 3 markdown files (PLAN.md, PROGRESS.md, CONTEXT.md). Use when starting large features, multi-session work, or complex refactoring. Auto-tracks commits in PROGRESS.md.
- License 许可
- MIT
- 最近更新
- 2026-06-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- persistent-planning
- description
- Persistent planning system with 3 markdown files (PLAN.md, PROGRESS.md, CONTEXT.md). Use when starting large features, multi-session work, or complex refactoring. Auto-tracks commits in PROGRESS.md.
- user-invocable
- false
03 SKILL.md 正文
Persistent Planning System
Overview
Use 3 persistent markdown files to track plans across sessions:
thoughts/PLAN.md- Active planthoughts/PROGRESS.md- Auto-tracked progress (commits)thoughts/CONTEXT.md- Project context and constraints
When to Create Plans
- Multi-file features (3+ files)
- Multi-session work
- Complex refactoring
- Architectural changes
PLAN.md Format
# Plan: [Feature Name]
## Goal
What we're building and why.
## Steps
1. [ ] Step one
2. [ ] Step two
3. [ ] Step three
## Constraints
- Must be backward compatible
- Must pass existing tests
## Status
IN PROGRESS | COMPLETED | BLOCKED
CONTEXT.md Format
# Project Context
## Architecture Decisions
- Using X because Y
- Chose A over B because C
## Key Files
- src/auth.ts - Authentication logic
- src/api/ - API endpoints
## Known Issues
- Rate limiting not implemented yet
How It Works
- Session start: If
thoughts/PLAN.mdexists, it's injected into context - After commits:
thoughts/PROGRESS.mdis auto-updated with commit hash and message - Plan completion: Update PLAN.md status to COMPLETED
Notes
- Plans are project-local (in the project's
thoughts/directory) - PROGRESS.md is append-only (never loses history)
- Add
thoughts/to.gitignoreif you don't want plans in version control
04 同仓库更多 Skills
workflow-router
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
wiring
Wiring Verification
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
visual-verdict
Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.
verification-loop
Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.
vector-db-patterns
Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.