Vinix24/vnx-orchestration / skills/planner
planner
VerifiedPlanning specialist that breaks a VNX feature or track into small, independently-shippable PRs with dependencies and per-PR task-class routing. USE THIS when the user wants to break a feature down into PRs, sequence the work, or turn a plan into a PR queue. Delegated to by @horizon (formerly @pm — @pm still resolves via alias). Works from Horizon's tracks DB (`vnx horizon`, alias `vnx objective`); the repo FEATURE_PLAN.md is a generated generic example, not the source.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.4 KB |
| references/_MAPPING.md | markdown | 355 B |
| scripts/intelligence.shexecutable | script | 1.3 KB |
| template.md | markdown | 1.5 KB |
template.md
View on GitHub# Planner Report Template
## Output Location
Write your report to: `$VNX_DATA_DIR/unified_reports/`
## Filename Format
`{timestamp}-{track}-plan-{title}.md`
Example: `20260202-143000-A-plan-authentication-system.md`
## Report Structure
### Executive Summary
High-level overview of the plan and expected outcomes (3-4 sentences)
### Tags (Required)
- [tag1, tag2, tag3] # Use specific, compound tags (e.g., sse-streaming, browser-pool, kvk-validation). Avoid general-only tags.
### Strategic Plan
- Project goals and objectives
- Success criteria
- Key deliverables
- Timeline and milestones
### Technical Approach
- Architecture decisions
- Technology choices
- Design patterns to use
- Integration points
### Implementation Phases
1. **Phase 1**: [Description, duration, deliverables]
2. **Phase 2**: [Description, duration, deliverables]
3. **Phase 3**: [Description, duration, deliverables]
### Resource Requirements
- Team composition needed
- Technical resources
- External dependencies
- Time estimates
### Risk Assessment
- Technical risks
- Mitigation strategies
- Contingency plans
### Recommendations
- Immediate next steps
- Priority order
- Success metrics
- Review checkpoints
### Intelligence Feedback
<!-- If your dispatch included [INTELLIGENCE_DATA] with offered_pattern_hashes, report which patterns you actually used: -->
used_pattern_hashes: []
## Quality Standards
- Include clear phase boundaries
- Define measurable success criteria
- Identify dependencies explicitly
- Provide realistic time estimates
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |