Skip to content
Back to skills

Sdd Tasks

ASecurity

Dependency-ordered task breakdown for spec-driven development

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
ai-agents

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add PedroMosquera/squadai --skill sdd-tasks --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sdd Tasks?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sdd Tasks
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pedromosquera-sdd-tasks/badge)](https://www.skillsdirectory.com/skills/pedromosquera-sdd-tasks)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sdd-tasks
description: Dependency-ordered task breakdown for spec-driven development
methodology: sdd
---

# SDD Tasks Skill

Break a design into a dependency-ordered list of implementation tasks.
Each task must be independently completable and testable.

## Steps

1. **Identify leaf-level tasks**: Find the smallest independently implementable units.
   - Each task should produce a working, tested component
   - Tasks should be completable in 30 min to 4 hours
   - Tasks that cannot be tested independently need to be split further

2. **Identify dependencies**: Map which tasks depend on others.
   - Task B depends on Task A if B requires A's output to compile or run
   - Mark dependencies explicitly (not just "nice to have A first")
   - Identify the critical path (longest chain of dependencies)

3. **Build a dependency graph**: Visualize the execution order.
   ```
   Task 1 (no deps)
   Task 2 (no deps)
   Task 3 (depends: Task 1)
   Task 4 (depends: Task 1, Task 2)
   Task 5 (depends: Task 3, Task 4)
   ```

4. **Group into phases**: Batch independent tasks for parallel execution.
   - Phase 1: Tasks with no dependencies
   - Phase 2: Tasks whose dependencies are complete after Phase 1
   - Continue until all tasks are assigned

5. **Estimate effort**: Assign complexity to each task.
   - **S** (Simple): ≤ 30 min, single function, no new abstraction
   - **M** (Medium): 30 min to 2 hrs, new type or interface, some design needed
   - **L** (Large): 2 to 4 hrs, multiple components, requires careful integration
   - Tasks estimated **L** or larger should be split if possible

6. **Write acceptance criteria per task**: Each task needs a clear done condition.
   - What tests must pass?
   - What behavior must be observable?
   - What artifacts must exist (new file, new type, updated interface)?

## Output Format

```
## Task Plan: <feature name>

### Dependency Graph
```
<ASCII or text dependency diagram>
```

### Phase 1 (parallel)
- [ ] Task 1: <description> [S]
  Depends on: none
  Done when: <acceptance criteria>

- [ ] Task 2: <description> [M]
  Depends on: none
  Done when: <acceptance criteria>

### Phase 2 (parallel after Phase 1)
- [ ] Task 3: <description> [M]
  Depends on: Task 1
  Done when: <acceptance criteria>

### Summary
| Phase | Tasks | Effort |
|-------|-------|--------|
| 1 | 2 | S+M |
| 2 | 1 | M |
| Total | 3 | ~3-4 hrs |
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…