MrPointer/planning-project-features
dot_agents/skills/planning-project-features/SKILL.md
Route feature planning to the correct workflow. Recommends RFC-first design when no RFC exists, sends reviewed RFCs to RFC-backed planning, and sends explicit opt-outs to direct planning.
$ install --global
skillsauthnpx skillsauth add MrPointer/dotfiles planning-project-featuresInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 9, 2026, 2:23 AM178.8s1 file scanned
SKILL.md
- name:
- planning-project-features
- description:
- Route feature planning to the correct workflow. Recommends RFC-first design when no RFC exists, sends reviewed RFCs to RFC-backed planning, and sends explicit opt-outs to direct planning.
Planning Project Features
Route feature planning deterministically. This skill does not create plans itself; it chooses the correct planning workflow and then stops or delegates.
Routing Table
| Input State | Action | Planning Workflow | Reviewers |
|-------------|--------|-------------------|-----------|
| Reviewed RFC provided | Validate the RFC review record, then use the RFC as the design baseline | planning-project-features-from-rfc | plan-rfc-fidelity-reviewer, plan-executability-reviewer |
| RFC provided but not reviewed | Stop and offer two choices: review the RFC first, or proceed as direct planning | authoring-rfcs review or planning-project-features-direct | Depends on chosen path |
| No RFC provided | Recommend creating an RFC first, then ask whether to create one or continue directly | brainstorming + authoring-rfcs, or planning-project-features-direct | Depends on chosen path |
Workflow
Step 1: Check For An RFC
If the user provides or references an RFC, read it and inspect its Review Record.
A reviewed RFC has:
rfc-architect-reviewerwith statusPassedorPassed with concerns.rfc-risk-reviewerwith statusPassedorPassed with concerns.- No
Blockingreview status that affects decomposition, scope, contracts, migration, rollout, acceptance criteria, or implementation constraints.
If these conditions hold, use planning-project-features-from-rfc. Do not re-gather requirements or re-litigate the RFC design.
If an RFC exists but does not meet these conditions, stop and present exactly two choices:
- Review or revise the RFC first with
authoring-rfcs. - Proceed with direct planning using
planning-project-features-direct, treating the RFC as background context rather than an approved baseline.
Step 2: Recommend RFC-First When Missing
If no RFC exists, recommend creating one before planning. Explain the concrete benefits briefly:
- It separates design decisions from execution decomposition.
- It gives architecture and risk reviewers the right artifact to review.
- It gives planning a stable, reviewed baseline instead of forcing it to rediscover the design.
- It reduces token waste in planning by narrowing plan review to fidelity and executability.
- It creates a stable RFC document reference for future plans, implementation sessions, and follow-up discussion.
- It preserves user-approved decisions so the planner does not reopen them accidentally.
Then ask the user to choose exactly one path:
- Create or finish the RFC first with
brainstormingandauthoring-rfcs. - Continue directly with
planning-project-features-direct.
Do not continue silently. The user chooses the route.
Step 3: Delegate
After the route is chosen, load exactly one workflow skill:
planning-project-features-from-rfcfor reviewed RFC-backed planning.planning-project-features-directfor direct planning.brainstormingand thenauthoring-rfcswhen the user chooses RFC-first design work.
Do not mix workflows in one planning run.
Rules
- Do not create plans in this router skill.
- Do not make conditional reviewer choices here.
- Do not treat an unreviewed RFC as an approved design baseline.
- Do not ask the user to repeat information already present in a reviewed RFC.
- If the chosen path becomes invalid, stop and return to the routing table.
Related Skills
MrPointer/skill-creator
testing
VerifiedTrustedCommunity
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
2SKILL.mdUpdated Jun 8, 2026
MrPointer/planning-project-features-from-rfc
testing
VerifiedTrustedCommunity
Create implementation plans from a reviewed RFC. Uses the RFC as the approved design baseline, decomposes it into executable sub-plans, and runs RFC-specific plan review.
2SKILL.mdUpdated May 8, 2026
MrPointer/planning-project-features-direct
tools
VerifiedTrustedCommunity
Create implementation plans directly from user requirements when no reviewed RFC is available or the user explicitly declines RFC-first planning. Decomposes work into self-contained sub-plans with full iterative multi-agent plan review.
2SKILL.mdUpdated May 8, 2026
MrPointer/planning-project-epics-from-rfc
content-media
VerifiedTrustedCommunity
Decompose a reviewed RFC into sequenced features for a single project. Uses the RFC as the approved design baseline and produces a persistent epic plan reviewed for RFC fidelity and feature decomposition.
2SKILL.mdUpdated May 8, 2026