Copy one prompt into Cursor, Copilot, Kilo, or any agent with web access.
Install the Neexo skill "Neexo Feature Planning Skill" (plan-feature-change) in this repository.
Manifest: https://awesome.neexo.dk/api/install-manifest?ids=skills%2Fplan-feature-change
Catalog: https://awesome.neexo.dk/skills/plan-feature-change
Steps:
1. Fetch https://awesome.neexo.dk/api/install-manifest?ids=skills%2Fplan-feature-change and read the file list.
2. Fetch https://awesome.neexo.dk/api/skills/plan-feature-change/bundle and write every file to the correct project skill folder.
3. Detect IDE from this repo (.cursor → Cursor, .kilo → Kilo).
4. Preserve subdirectory structure (references/, agents/, scripts/, assets/).
5. Confirm which files you wrote.
Copilot — full plugincopilot plugin install neexo-planning@awesome-neexo
Bundle API (JSON)https://awesome.neexo.dk/api/skills/plan-feature-change/bundle
Overview
Use this skill before implementation when a feature crosses multiple modules or touches high-risk areas.
When to Plan
Feature touches 3+ modules or services
Database schema changes are required
Auth, billing, or tenant isolation is affected
Breaking changes to APIs or data formats
Rollback would be difficult without a plan
Output Template
1. Goal and Non-Goals
Goal: what this feature delivers to the user
Non-goals: what is explicitly out of scope
2. Files and Ownership
List the files/modules that will be modified and who owns each area.
3. Data and Schema Changes
New tables, columns, or indexes
Migration strategy (additive-only preferred)
Backward compatibility with existing data
4. Auth and Validation
Which endpoints need role checks
Input validation rules
Tenant scoping implications
5. Test Plan
Unit tests for business logic
Integration tests for cross-module flows
E2E tests for user-facing scenarios
Edge cases to cover
6. Rollout and Migration Risks
Feature flag strategy
Database migration ordering (migration SQL must ship with code)
Rollback plan if deployment fails
Monitoring and alerting changes
7. Open Questions
List unresolved decisions that need input before implementation starts.
Raw content
Copy into your project — e.g. .instructions.md, .agent.md, or SKILL.md
## Overview
Use this skill before implementation when a feature crosses multiple modules or touches high-risk areas.
## When to Plan
- Feature touches 3+ modules or services
- Database schema changes are required
- Auth, billing, or tenant isolation is affected
- Breaking changes to APIs or data formats
- Rollback would be difficult without a plan
## Output Template
### 1. Goal and Non-Goals
- **Goal**: what this feature delivers to the user
- **Non-goals**: what is explicitly out of scope
### 2. Files and Ownership
List the files/modules that will be modified and who owns each area.
### 3. Data and Schema Changes
- New tables, columns, or indexes
- Migration strategy (additive-only preferred)
- Backward compatibility with existing data
### 4. Auth and Validation
- Which endpoints need role checks
- Input validation rules
- Tenant scoping implications
### 5. Test Plan
- Unit tests for business logic
- Integration tests for cross-module flows
- E2E tests for user-facing scenarios
- Edge cases to cover
### 6. Rollout and Migration Risks
- Feature flag strategy
- Database migration ordering (migration SQL must ship with code)
- Rollback plan if deployment fails
- Monitoring and alerting changes
### 7. Open Questions
List unresolved decisions that need input before implementation starts.