Menu
Two-layer feature planning (business + technical). Use when planning any feature before implementation starts.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | implementation-planning |
| description | Two-layer feature planning (business + technical). Use when planning any feature before implementation starts. |
| auto_load | true |
| priority | high |
When planning a feature before implementation starts.
Every feature plan has two layers:
Layer A: Non-Technical Summary
Layer B: Technical Detail
Make them specific and testable:
Good:
- [ ] User can select a coach from a list
- [ ] System prevents booking overlapping sessions
- [ ] All tests pass
Bad:
- [ ] Booking system works
- [ ] It's fast
Break large features into smaller issues:
Blocker:
Warning:
Code review standards for automated and manual reviews. Use when reviewing code changes.
Ensure documentation stays in sync with code changes. Trigger when modifying CLI commands, config options, directory structure, or public APIs.
Git branch naming, commit conventions, and PR workflow. Use for all git operations.
Comprehensive security vulnerability scanning and OWASP Top 10 compliance checking. Use when reviewing code for security issues, validating authentication/authorization, or ensuring security best practices.
Comprehensive patterns for writing robust non-brittle tests including eliminating waitForTimeout, mocking time properly, and generating unique test data. Use when writing any tests to ensure fast reliable maintainable test suites.
TDD patterns, Jest testing conventions, and test quality standards. Use when writing any tests.