cost-based-planner
Plan coding work with minimal context, relevant file selection, risk awareness, rollback, and validation strategy.
- License 许可
- MIT
- 所属仓库
- domehahn/skcr
- 最近更新
- 2026-09-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- cost-based-planner
- since
- 2026-06-10
- authors
- [ "platform-engineering" ]
- version
- 1.1.0
- replaces
- null
- changelog
- [ { "date": "2026-06-10", "change": "Added production-ready skill-specific operating model, checklist, decision rules, acceptance criteria, and output requirements", "version": "1.1.0" }, { "date": "2025-01-01", "change": "Initial release", "version": "1.0.0" } ]
- stability
- stable
- supersedes
- []
- description
- Plan coding work with minimal context, relevant file selection, risk awareness, rollback, and validation strategy.
- last_modified
- 2026-06-10
- deprecated_since
- null
- min_platform_version
- { "kiro": "unknown", "codex": "unknown", "junie": "unknown", "cursor": "unknown", "ollama": "unknown", "opencode": "unknown", "roo-code": "unknown", "windsurf": "unknown", "openhands": "unknown", "gemini-cli": "unknown", "gitlab-duo": "unknown", "claude-code": "unknown", "github-copilot": "unknown" }
02 资源文件 6
- 参考文档CHANGELOG.md190 B
- 许可证LICENSE214 B
- 参考文档README.md347 B
- 参考文档skill.yaml416 B
- 参考文档tests/README.md94 B
- 其他VERSION6 B
03 SKILL.md 正文
Cost Based Planner
Purpose
Plan coding work with minimal context, relevant file selection, risk awareness, rollback, and validation strategy.
When to use
Use this skill when the task matches the description above or when the central agent instructions route work to $cost-based-planner.
Operating model
- Clarify the goal and constraints.
- Inspect the minimum relevant repository context.
- Produce a concise execution plan for non-trivial work.
- Execute with tools when implementation is requested.
- Validate the result with repository-native checks.
- Summarize changed files, validation results, and residual risks.
DevSecOps guardrails
- Do not read secrets,
.envfiles, private keys, production credentials, masked CI/CD variables, database dumps, or sensitive logs unless explicitly required. - Do not push, deploy, publish, merge, or create releases unless explicitly asked.
- Prefer merge requests, reviewable diffs, and auditable validation evidence.
- Prefer least privilege, minimal changes, and explicit rollback notes.
- Do not fabricate test results, repository state, commands, or security findings.
Skill-Specific Operating Model
- Start from the user goal and identify the smallest useful set of files, commands, and decisions needed to reduce uncertainty.
- Budget context deliberately: read high-signal entry points, tests, configs, and recent diffs before broad exploration.
- Split work into reversible steps with validation after risky changes.
Skill-Specific Checklist
- Scope, non-goals, constraints, and affected surfaces are explicit.
- Relevant files are selected by references, tests, ownership, execution path, and risk.
- Rollback and validation are matched to data, security, compatibility, and user-facing impact.
Decision Rules
- Ask clarification only when repository context cannot support a safe assumption.
- Read more before editing shared contracts, auth, persistence, release, or generated output.
- Do not minimize context so aggressively that a high-risk dependency is missed.
Acceptance Criteria
- The plan states what will change, what will not change, and how success will be checked.
- High-risk areas have mitigation, validation, or explicit out-of-scope treatment.
- The plan can be converted directly into implementation steps.
Output Requirements
- Provide concise ordered steps with status for ongoing work.
- Name anchor files/directories and validation commands.
- Include assumptions, blockers, and rollback notes.
Changelog
1.1.0 - 2026-06-10
- Added production-ready skill-specific operating model, checklist, decision rules, acceptance criteria, and output requirements.
1.0.0 - 2025-01-01
- Initial release.
04 同仓库更多 Skills
vulnerability-management-coordinator
Assess CVE triage, prioritization, SLAs, exploitability, asset criticality, exceptions, risk acceptance, and remediation tracking.
verification-reviewer
Review diffs, validate acceptance criteria, inspect test results, and find missed requirements.
universal-skill-creator
Create, adapt, validate, and optimize reusable agent skills across agentic platforms.
threat-modeler
Identify assets, trust boundaries, abuse cases, attack paths, threats, and required security controls.
test-strategy-engineer
Design and generate unit, integration, regression, security, and end-to-end test strategies.
sre-reliability-reviewer
Assess SLOs, SLIs, error budgets, capacity, degradation, timeouts, retries, circuit breakers, load shedding, and operational risks.