feature-plan
Automates the transition of software features from Pendente to Planejado by coordinating child user stories.
Install
mkdir -p .claude/skills/feature-plan && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13325" && unzip -o skill.zip -d .claude/skills/feature-plan && rm skill.zipInstalls to .claude/skills/feature-plan
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when the user asks to plan a Foundation SoftwareFeature — orchestrates planning of all child UserStories via /userstory-plan, then moves the Feature from "Pendente" to "Planejado". Skill name follows entity-action convention.Key capabilities
- →Transition a SoftwareFeature from Pendente to Planejado status
- →Orchestrate planning of all child UserStories
- →Load Feature and child UserStory details
- →Validate observable contracts for Features
- →Map coverage gaps between Feature success criteria and UserStory capabilities
- →Persist the updated status of the Feature
How it works
The skill transitions a SoftwareFeature from 'Pendente' to 'Planejado' by loading its details and child UserStories, validating contracts, mapping coverage gaps, and invoking `/userstory-plan` for each eligible UserStory. It then updates the Feature's status.
Inputs & outputs
When to use feature-plan
- →Plan a new software feature
- →Organize user story implementation
- →Update feature status to Planejado
About feature-plan
This skill guides a SoftwareFeature through the transition from Pendente to Planejado. It automates the orchestration of child UserStories and ensures project-wide consistency by validating contracts and acceptance criteria.
Use when the user asks to plan a Foundation SoftwareFeature — orchestrates planning of all child UserStories via /userstory-plan, then moves the Feature from "Pendente" to "Planejado". Skill name follows entity-action convention.
When not to use it
- →To plan a single UserStory
- →To implement a Feature after planning
- →To create UserStories from existing code
Limitations
- →The skill only covers the transition from Pendente to Planejado
- →It does not invent User Stories
- →It ignores User Stories already in 'Pronto para Dev' or later stages
How it compares
This skill automates the complex orchestration of planning a SoftwareFeature and its associated UserStories, ensuring consistency and validation across the project, unlike a manual, fragmented planning process.
Compared to similar skills
feature-plan side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| feature-plan (this skill) | 0 | 6mo | No flags | Advanced |
| trello | 41 | 6mo | Review | Beginner |
| executing-plans | 6 | 6mo | No flags | Intermediate |
| github-project-management | 4 | 9mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
trello
openclaw
Manage Trello boards, lists, and cards via the Trello REST API.
executing-plans
obra
Use when you have a written implementation plan to execute in a separate session with review checkpoints
github-project-management
ruvnet
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
project-clickup
incidentfox
ClickUp project management integration for incident tracking and task management
coo-advisor
alirezarezvani
Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.
tlc-spec-driven
tech-leads-club
Project and feature planning with 4 phases - Specify, Design, Tasks, Implement+Validate. Creates atomic tasks with verification criteria and maintains persistent memory across sessions. Stack-agnostic. Use when: (1) Starting new projects (initialize vision, goals, roadmap), (2) Working with existing codebases (map stack, architecture, conventions), (3) Planning features (requirements, design, task breakdown), (4) Implementing with verification, (5) Tracking decisions/blockers across sessions, (6) Pausing/resuming work. Triggers on "initialize project", "map codebase", "specify feature", "design", "tasks", "implement", "pause work", "resume work".