concise-planning
Generate actionable coding task plans
Turn vague project requests into structured, executable checklists. Reduce back-and-forth by making reasonable assumptions and providing atomic, verb-first action items.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "concise-planning". Plan to add pagination to our product listing endpoint
Expected outcome:
- # Plan
- Implement offset-based pagination for the GET /products endpoint with configurable page size and sorting options.
- ## Scope
- - In: Product listing endpoint, response format, query parameters
- - Out: Other endpoints, caching layer, frontend changes
- ## Action Items
- [ ] Review current GET /products implementation in src/routes/products.ts
- [ ] Add query parameters: page, limit, sortBy, sortOrder
- [ ] Implement offset calculation and database query modification
- [ ] Add pagination metadata to response (total, page, totalPages)
- [ ] Write unit tests for pagination logic
- [ ] Add integration test verifying correct page contents
- [ ] Update API documentation
- [ ] Test with edge cases (empty results, last page, invalid params)
- ## Open Questions
- - What is the default page size? (Assuming 20)
- - Should we implement cursor-based pagination for large datasets?
Using "concise-planning". Plan to upgrade our Django project from version 3.2 to 4.2 LTS
Expected outcome:
- # Plan
- Execute a major version upgrade following Django's deprecation path with testing at each stage.
- ## Scope
- - In: Django core, installed Django packages, test suite
- - Out: Third-party services, deployment infrastructure, Python version
- ## Action Items
- [ ] Audit installed packages for Django 4.x compatibility
- [ ] Run tests on Django 3.2 to establish baseline
- [ ] Upgrade to Django 4.0, fix deprecation warnings
- [ ] Upgrade to Django 4.1, fix deprecation warnings
- [ ] Upgrade to Django 4.2 LTS, verify all tests pass
- [ ] Update requirements.txt and lock file
- [ ] Review Django 4.2 release notes for security considerations
- [ ] Deploy to staging environment for integration testing
- ## Open Questions
- - Are there custom middleware or authentication backends that may be affected?
- - What is the rollback plan if issues surface in production?
Security Audit
SafeStatic analyzer flagged 4 patterns that are all false positives. The external_commands detections at lines 18 and 37 are markdown formatting (inline code and code fences), not shell execution. The cryptographic algorithm detections at lines 3 and 67 are plain documentation text with no actual crypto operations. This skill is purely a planning template with no executable code, network access, or system interactions.
Quality Score
What You Can Build
Feature Development Planning
Break down new feature requests into discrete, implementable steps with clear validation criteria.
Refactoring Projects
Create structured plans for codebase improvements with defined scope and rollback considerations.
Bug Investigation
Generate systematic debugging plans that cover discovery, hypothesis testing, and verification.
Try These Prompts
Create a plan to add user authentication to our Express API. We use PostgreSQL and JWT. Include discovery, implementation, and testing steps.
Plan a refactoring of our monolithic UserService into separate modules for authentication, profile management, and notifications. Current file is src/services/user.ts (450 lines). Define clear scope boundaries and migration approach.
Users report intermittent 500 errors on checkout. Create an investigation plan covering log analysis, reproduction steps, hypothesis testing, and monitoring setup. Payment provider is Stripe.
Plan our migration from REST to GraphQL for the product catalog API. Include schema design, resolver implementation, gradual rollout strategy, and deprecation timeline for existing endpoints.
Best Practices
- Start with context gathering - read README, docs, and relevant code before planning
- Keep action items atomic - each should be a single logical unit of work
- Always include validation or testing as explicit steps in the plan
Avoid
- Creating plans without understanding the existing codebase structure
- Writing vague steps like 'fix the issue' instead of concrete actions
- Skipping validation steps or assuming testing will happen separately