ederfmatos/claude-voice-bridge / .claude/skills/cy-create-tasks
cy-create-tasks
VerifiedDecomposes PRDs and TechSpecs into detailed, independently implementable task files with enrichment from codebase exploration. Use when a PRD or TechSpec exists and needs to be broken down into executable tasks, or when task files need enrichment with implementation context. Do not use for PRD creation, TechSpec generation, or direct task execution.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.5 KB |
| references/task-context-schema.md | markdown | 2.5 KB |
| references/task-template.md | markdown | 2.7 KB |
references/task-template.md
View on GitHub# Task File Template
Use this structure for every individual task file. The file must start with YAML frontmatter containing the parseable metadata.
```markdown
---
status: pending
title: [Task title]
type: [one of frontend, backend, docs, test, infra, refactor, chore, bugfix, or a project-specific [tasks].types override]
complexity: [low, medium, high, critical]
---
# Task N: [Title]
## Overview
[2-3 sentences: what the task accomplishes and why it matters in the context of the project.]
<critical>
- ALWAYS READ the PRD and TechSpec before starting
- REFERENCE TECHSPEC for implementation details — do not duplicate here
- FOCUS ON "WHAT" — describe what needs to be accomplished, not how
- MINIMIZE CODE — show code only to illustrate current structure or problem areas
- TESTS REQUIRED — every task MUST include tests in deliverables
</critical>
<requirements>
- [Requirement 1 — specific technical requirement]
- [Requirement 2 — e.g., "MUST authenticate users via JWT tokens"]
- [Requirement 3]
</requirements>
## Subtasks
- [ ] N.1 [Subtask description — WHAT to accomplish]
- [ ] N.2 [Subtask description]
- [ ] N.3 [Subtask description]
## Implementation Details
[File paths to create or modify and integration points.
Reference the TechSpec implementation section for code patterns and interface designs.]
### Relevant Files
- `path/to/file` — [brief reason this file is relevant]
### Dependent Files
- `path/to/dependency` — [brief reason this file is affected]
### Related ADRs
- [ADR-NNN: Title](../adrs/adr-NNN.md) — Relevance to this task
## Deliverables
- [Concrete output 1]
- [Concrete output 2]
- Unit tests with 80%+ coverage **(REQUIRED)**
- Integration tests for [feature] **(REQUIRED)**
## Tests
- Unit tests:
- [ ] [Test case 1 — e.g., "Happy path: valid input returns expected output"]
- [ ] [Test case 2 — e.g., "Error path: invalid input returns descriptive error"]
- [ ] [Edge cases and boundary conditions]
- Integration tests:
- [ ] [Test case — e.g., "End-to-end flow from request to response"]
- Test coverage target: >=80%
- All tests must pass
## Success Criteria
- All tests passing
- Test coverage >=80%
- [Measurable outcome 1]
- [Measurable outcome 2]
```
## Guidelines
- Every task must be independently implementable when its dependencies from `_tasks.md` graph edges are met.
- Every task MUST include a Tests section and test items in Deliverables.
- Never create separate tasks dedicated solely to testing.
- Subtasks describe WHAT needs to happen, not HOW to implement it.
- Minimize code in tasks. Show code only to illustrate current structure or problem areas.
- Implementation details should reference the TechSpec for patterns rather than duplicating them.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |