Menu
Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.
Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/stella/.github --skill planO comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Review and update third-party dependencies. Use this when asked to upgrade packages, survey new minor or major releases for useful features, assess whether a repository can adopt them, or validate whether a release looks suspicious before bumping it.
Shape a feature or problem before implementation. Use this when the request is still fuzzy, when several solutions are possible, or when execution risks outrunning product clarity.
Process automated PR review comments systematically. Use this for CodeRabbit, Gemini, GitHub Copilot, Devin, Greptile, and similar bots.
Exibindo SKILL.md
| name | plan |
| description | Create a new implementation plan in the repo's planning area. |
Create a new implementation plan in the repo's planning area.
$ARGUMENTS — A short slug for the plan, ideally kebab-case. If empty, derive a reasonable slug from the task.
Prefer this shared planning layout when the repo supports it:
.agents/ARCHITECTURE.md
.agents/GOALS.md
.agents/STATUS.md
.agents/plans/
If the repo uses a different planning area, adapt to it rather than creating duplicate systems.
Read planning context:
.agents/ARCHITECTURE.md if present.agents/GOALS.md if presentDetermine the plan location:
.agents/plans/Determine the next plan number:
ls .agents/plans/
Use the next sequential number when numbered plans are already in use. If the repo does not number plans, follow its established naming.
Research before writing:
Write the plan with this structure:
# Plan: [Feature Name]
Date: YYYY-MM-DD
## Goal
What are we building and why?
## Design Decisions
- **Decision**: Why this approach over alternatives.
## Scope
**In scope:**
- ...
**Out of scope:**
- ...
## Implementation
- `path/to/file` — what changes here
## Test Cases
What needs to be verified.
## Open Questions
Any unresolved decisions.
Plan well, do not over-specify:
Confirm before finalizing if the user is still shaping the task. If they asked you to just create the plan, go ahead and write it.