From example-skills
Personal multi-project coordination for creative practitioners managing many concurrent initiatives. Not PM methodology—practical systems for tracking progress, managing energy, and moving projects forward. Triggers on project management, multi-project coordination, progress tracking, or overwhelm with concurrent work.
npx claudepluginhub organvm-iv-taxis/a-i--skills --plugin document-skillsThis skill uses the workspace's default tool permissions.
Manage many projects without losing your mind.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.
Manage many projects without losing your mind.
| Traditional PM | Personal Orchestration |
|---|---|
| Timelines and deadlines | Energy and momentum |
| Resource allocation | Attention allocation |
| Status reporting | Progress awareness |
| Team coordination | Self-coordination |
| External accountability | Internal systems |
┌─────────────────────────────────────────────────┐
│ ACTIVE │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ Primary │ │Secondary│ │ Support │ │
│ │ (1-2) │ │ (2-3) │ │ (many) │ │
│ └─────────┘ └─────────┘ └─────────┘ │
└─────────────────────────────────────────────────┘
▲ │
│ ▼
┌─────────────┐ ┌─────────────┐
│ WAITING │ │ DORMANT │
│ (blocked) │ │ (paused) │
└─────────────┘ └─────────────┘
▲ │
│ ▼
│ ┌─────────────┐
└────────────────────│ ARCHIVED │
│ (complete) │
└─────────────┘
| State | Definition | Attention |
|---|---|---|
| Primary | Active daily work | Deep focus |
| Secondary | Regular progress | Scheduled time |
| Support | Maintenance mode | As needed |
| Waiting | Blocked on external | Check-in only |
| Dormant | Intentionally paused | Monthly review |
| Archived | Complete or abandoned | None |
1. CLEAR (15 min)
- Process inbox
- Update project statuses
- Log completions
2. REFLECT (15 min)
- What moved forward?
- What's stuck?
- What drained vs energized?
3. DECIDE (15 min)
- Primary focus for next week
- Must-do items
- Might-do if energy allows
4. PREPARE (15 min)
- Next actions are clear
- Blocks identified
- Environment ready
Morning:
- What's the ONE thing today?
- What state am I in? (energy/focus)
- What might derail me?
Evening:
- Did the thing happen?
- What surprised me?
- Tomorrow's one thing?
For each project, know:
## [Project Name]
**State**: [Primary/Secondary/Support/Waiting/Dormant]
**One-liner**: What is this?
**Next Action**: The very next physical action
**Waiting For**: (if blocked) What/who/when
**Last Touched**: [Date]
| Project | State | Next Action | Blocked? | Last Touched |
|---|---|---|---|---|
| [Name] | Primary | [Action] | No | Today |
| [Name] | Secondary | [Action] | Yes: [reason] | 3 days ago |
| [Name] | Dormant | - | - | 2 weeks ago |
Simple traffic light:
| Status | Meaning |
|---|---|
| 🟢 | Moving, on track |
| 🟡 | Slow, needs attention |
| 🔴 | Stuck, needs intervention |
| ⚪ | Intentionally paused |
| State | Suitable Work |
|---|---|
| High Focus | Complex creative work, writing, coding |
| Medium Focus | Editing, planning, correspondence |
| Low Focus | Admin, organizing, routine tasks |
| Recovery | Rest, input, inspiration |
Don't fight your energy. Match work to state.
High Energy → Primary project deep work
Medium Energy → Secondary project progress
Low Energy → Support tasks, admin
No Energy → Rest or quit for the day
| Block | Signal | Intervention |
|---|---|---|
| Unclear next action | Avoiding project | Define smallest step |
| Fear of failure | Procrastination | Lower stakes, draft mode |
| Perfectionism | Endless revision | Ship deadline |
| Overwhelm | Paralysis | Reduce scope |
| Boredom | No progress | Find the interesting part |
| External dependency | Waiting | Follow up or route around |
1. Name the block (what specifically is stuck?)
2. Identify the feeling (fear? confusion? boredom?)
3. Find the smallest action (2-minute version)
4. Do that action now
5. Reassess
Pause when:
Push when:
Ending a work session:
1. Write down exactly where you are
2. Note the next action
3. Leave breadcrumbs (comments, notes)
4. Mental "close" ritual
Starting a work session:
1. Read your previous notes
2. Review recent work (5 min)
3. Start with smallest action
4. Build momentum before diving deep
Time blocking: Dedicate days/half-days to projects
Mon: Project A (Primary)
Tue: Project A (Primary)
Wed: Project B (Secondary)
Thu: Project A (Primary)
Fri: Admin + Secondary projects
Energy blocking: Match projects to energy patterns
Morning (high focus): Primary project
Afternoon (medium): Secondary projects
Evening (low): Support tasks
Theme days: Group similar work
Mon: Deep creative work
Tue: Communication + meetings
Wed: Deep creative work
Thu: Learning + input
Fri: Admin + planning
1. Capture the spark (what excites you?)
2. Define done (what does completion look like?)
3. Identify first milestone (what's the first "win"?)
4. List knowns and unknowns
5. Determine initial state (Primary? Secondary?)
6. Set review date
Regular questions:
- Is this still worth doing?
- Is the scope still right?
- Am I the right person?
- Is the timing still right?
Completion:
Abandonment (equally valid):
Must have:
Nice to have:
Avoid:
Minimal: Text file per project + master index Light: Single notes app with tags Medium: Notion/Obsidian with simple database Heavy: Full PM tool (only if you actually use it)
references/review-templates.md - Weekly/monthly/quarterly review templatesreferences/stuck-interventions.md - Detailed unsticking strategies