Borrowing it
Nothing to install: this file belongs to charliehzm/medharness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/charliehzm/medharness/main/.claude/skills/task-decomposition/SKILL.mdgit clone --depth 1 https://github.com/charliehzm/medharnessWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/charliehzm/medharness/task-decomposition)<a href="https://agentmods.dev/skills/charliehzm/medharness/task-decomposition"><img src="https://agentmods.dev/badge/skills/charliehzm/medharness/task-decomposition/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/charliehzm/medharness/task-decomposition"><img src="https://agentmods.dev/badge/skills/charliehzm/medharness/task-decomposition.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00159 | $0.00881 |
| Opus 5 | $0.00079 | $0.00441 |
| Sonnet 5 | $0.00032 | $0.00176 |
| Haiku 4.5 | $0.00016 | $0.00088 |
Grade A, and why
task-decomposition scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Task Decomposition
Translates an implementation-ready change into a queue of bite-sized tasks.
The canonical prompt (verbatim from v1 SOP)
将所有任务进行拆分，其中前端与后端任务要分开，每个任务不超过 2 个文件的改动，每个任务单独任务文档，任务按照优先级排序，任务文档名称和文件夹名称尽可能用中文。
Why these constraints
| Constraint | Why |
|---|---|
| ≤ 2 files | Forces tight blast radius; Agent stays focused; reviews are easy. |
| One doc per task | Audit / trace / parallel review without merge conflicts. |
| Chinese names | Project policy; improves PM legibility. |
| FE/BE separation | Different reviewers; different risk profiles; cleaner deploys. |
| Priority order | First task to clear must unlock the most downstream value. |
Output structure
openspec/changes/<slug>/
├── tasks.md # index, ordered list with links + status checkboxes
└── tasks/
├── 后端-01-用户匹配引擎雏形.md
├── 后端-02-匹配规则配置层.md
├── 前端-01-匹配结果展示页.md
└── ...
Each task document:
# 后端-01 · 用户匹配引擎雏形
- **状态**: [ ] 未开始 / [x] 已完成
- **优先级**: P0
- **依赖**: -
- **预计文件**:
- backend/match/engine.py (new)
- backend/match/__init__.py (edit)
- **Spec 引用**: S1-match-engine
- **验收**: <criteria>
- **风险**: <if any>
Workflow
- Walk specs/* — derive 1-N tasks per spec.
- Classify each task as Frontend / Backend / Both (Both is rare; usually splits into two tasks).
- Estimate files touched — if > 2, split further.
- Order by P0 → P3.
- Write per-task documents.
- Write tasks.md index linking to each.
Common failure modes
- Mega-task with 5 files — "refactor + add" combo. Mitigation: hard limit, refuse to write a task with > 2 files.
- No priority — "all P0". Mitigation: enforce at most 30% P0 of total.
- Cross-track dependency — frontend task waits on backend task, no annotation. Mitigation: dependencies field is required.
- English-only naming — "task-001-match-engine". Mitigation: project policy is Chinese; apply unless team agrees otherwise.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 86 lines · 159 tokens per session scan A 9fa6f00902ec
task-decomposition is a skill published in the GitHub repository charliehzm/medharness (86 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 159 tokens to every session and 881 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
hipaa-review
Performs a HIPAA Security Rule compliance review against all Administrative, Physical, and Technical Safeguards defined in 45 CFR Part 164, Subpart C. Auto-invoked when discussing healthcare data security, ePHI protection, HIPAA audit readiness, or business associate compliance. Evaluates required and addressable…
HIPAA Compliance Testing
Testing HIPAA compliance for healthcare applications including PHI handling, audit logging, access controls, and data encryption verification.
Healthcare Compliance
HIPAA compliance, healthcare regulations, privacy and security standards for medical organizations and providers.
compliance
Use when scoping which regulatory frameworks bind a business — SOC 2, ISO 27001, HIPAA, PCI DSS, EU AI Act, DORA, NIS2 — building a control register with owners and evidence, or standing up the cadence that keeps it audit-ready. NOT drafting privacy-policy/ROPA/DPA or ToS text (that is gdpr-privacy, terms-conditions)…
healthcare-expert
Expert-level healthcare systems, medical informatics, HIPAA compliance, and health data standards. Use when the user mentions medical, HIPAA, HL7, FHIR, or EHR, or when the task involves Healthcare IT, Standards and Protocols, Regulatory Compliance, or Security and Compliance.
performing-soc2-type2-audit-preparation
Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security…