技能 concise-planning
📦
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.
支持: Claude Codex Code(CC)
1
下载技能 ZIP
2
在 Claude 中上传
前往 设置 → 功能 → 技能 → 上传技能
3
开启并开始使用
测试它
正在使用“concise-planning”。 Plan to add pagination to our product listing endpoint
预期结果:
- # 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?
正在使用“concise-planning”。 Plan to upgrade our Django project from version 3.2 to 4.2 LTS
预期结果:
- # 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?
安全审计
安全v1 • 2/24/2026
Static 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.
1
已扫描文件
68
分析行数
0
发现项
1
审计总数
未发现安全问题
审计者: claude
质量评分
38
架构
100
可维护性
87
内容
22
社区
100
安全
91
规范符合性
你能构建什么
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.
试试这些提示
Basic Feature Plan
Create a plan to add user authentication to our Express API. We use PostgreSQL and JWT. Include discovery, implementation, and testing steps.
Refactoring Plan
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.
Bug Investigation Plan
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.
Migration Plan
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.
最佳实践
- 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
避免
- 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
常见问题
When should I use this skill versus asking directly for code?
Use this skill when starting a complex task that benefits from structured thinking. It helps you see the full scope before implementation begins and ensures nothing is overlooked.
How many action items should a plan include?
The skill generates 6-10 atomic items by default. This range balances completeness with cognitive load. Larger projects may need multiple plans at different abstraction levels.
Will the skill ask me questions before generating a plan?
The skill asks at most 1-2 questions and only when truly blocking. It makes reasonable assumptions for non-critical unknowns to minimize back-and-forth.
Can I modify the plan template structure?
The template provides a proven structure (Approach, Scope, Action Items, Validation). You can customize the sections in your prompt if your team has specific planning requirements.
Does this skill work for non-coding tasks?
While designed for development work, the structured approach applies to any project needing atomic steps. The verb-first, concrete format translates well to other domains.
What makes a good action item?
Good action items start with a verb (Add, Refactor, Verify), name specific files when possible, and represent a single logical unit of work that can be checked off when complete.