Plans
ProductivityplansPlans is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when working on implementation phases, checking phase status, or planning work. Provides context for the structured planning system in .plans/ folder.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/development/plans/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/plans, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Structured Planning System
This project uses a phased implementation approach. Plans are stored in .plans/ as markdown files with YAML front matter.
Phase Files Location
.plans/
├── README.md # Schema documentation
├── 00-foundation.md # Project setup, tokens, base layout
├── 01-threshold.md # Hero section + scroll transition
├── 02-navigation.md # Nav system + name-to-logo
├── 03-home-content.md # Bio, latest, footer sections
├── 04-work-page.md # Curated projects + archive
├── 05-about-page.md # Bio + artist statement
├── 06-press-page.md # Press grid + cards
└── 07-polish.md # Performance, a11y, deployment
Front Matter Schema
Each phase file has this structure:
---
phase: 0 # Numeric order (0-indexed)
title: "Phase Title" # Human-readable name
status: draft # draft | in-progress | blocked | review | complete
priority: P1 # P0 | P1 | P2 | P3
effort: medium # small | medium | large | xlarge
dependencies: [] # Array of phase numbers
blockers: [] # Blocking issues
started: null # ISO date
completed: null # ISO date
owner: null # Assignee
---
Status Values
| Status | Meaning |
|---|---|
draft | Defined but not actionable |
in-progress | Active development |
blocked | Cannot proceed |
review | Needs verification |
complete | Done and verified |
Working with Phases
Before Starting Work
- Read the phase file to understand scope
- Check dependencies are complete
- Update status to
in-progress - Add
starteddate
During Implementation
- Follow tasks in order
- Check off acceptance criteria as completed
- Note any blockers discovered
After Completing
- Verify all acceptance criteria met
- Update status to
complete - Add
completeddate - Check if this unblocks other phases
Commands
/plan-status— View all phase statuses/plan-next— Get next actionable phase/plan-start [phase]— Begin a phase/plan-complete [phase]— Mark phase done
Common Patterns
Reading a Phase
Read .plans/01-threshold.md to understand the threshold implementation requirements.
Updating Status
After completing work, edit the front matter:
status: complete
completed: 2024-01-15
Checking Dependencies
A phase is actionable when all items in its dependencies array have status: complete.
Tips
- Don't skip phases — dependencies exist for a reason
- Update status immediately when starting/completing
- If blocked, document the blocker and move on
- Review acceptance criteria before marking complete