Plan implementation
Configuração global do Cursor: user rules, agent skills, slash commands e hooks com scripts de instalação.
npx -y skills add JoaoAlavarse/cursor-config --skill plan-implementationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 15 days oldThe repository was created 15 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Analyzes a feature or change request and produces an inline implementation plan before writing code. Use for small, self-contained tasks that do not require a persistent workspace.
SKILL.md
2.5 KB, as published. Nobody here has run it
Objective
Analyze the requested feature, enhancement or change and produce a clear implementation plan.
Understand the problem before proposing a solution.
Use this skill for small, self-contained changes that can be planned and executed in a single interaction. For multi-file or multi-step tasks, use the create-working-plan skill instead.
Context
Before planning the implementation:
- If project rules are available, read and follow them.
- Otherwise, infer the project's conventions from the existing codebase.
- Respect the project's architecture, coding patterns, conventions and documented design decisions.
- Do not assume the project follows current best practices.
- Prefer solutions that fit naturally into the existing architecture.
Planning Process
- Understand the requested change.
- Identify assumptions and ambiguities.
- Identify the affected components.
- Analyze dependencies and potential side effects.
- Evaluate implementation options when meaningful trade-offs exist.
- Recommend the preferred approach and explain why.
- Break the work into logical implementation steps.
- Identify risks and validation requirements.
Do not begin implementing until the approach is sufficiently understood.
Planning Guidelines
Do not invent requirements.
Avoid unnecessary complexity.
Prefer incremental, reversible changes over large rewrites.
Reuse existing components, abstractions and patterns whenever appropriate.
Keep the plan concise and focused on implementation.
Clearly distinguish facts, assumptions and recommendations.
When multiple approaches are viable, explain the trade-offs and recommend one.
Do not generate implementation code unless explicitly requested.
Output
Summary
Briefly describe the recommended implementation strategy.
Assumptions
List any assumptions made during planning.
Affected Components
List the files, modules or systems likely to be affected.
Implementation Plan
Provide the implementation as an ordered list of steps.
Risks
Identify technical risks, edge cases or migration concerns.
Validation
Describe how the implementation should be verified.
Open Questions
List only questions that must be answered before implementation.