Back to skills
SkillHub ClubResearch & OpsFull StackTesting

test-aware-planner

A test-aware planning agent that generates tasks.md files with embedded test plans for one user story at a time, ensuring all acceptance criteria are covered with BDD-style scenarios and coverage targets to prevent crashes and maintain quality.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars
95
Hot score
94
Updated
March 20, 2026
Overall rating
C4.9
Composite score
4.9
Best-practice grade
B81.2

Install command

npx @skill-hub/cli install anton-abyzov-specweave-test-aware-planner

Repository

anton-abyzov/specweave

Skill path: plugins/specweave/skills/test-aware-planner

A test-aware planning agent that generates tasks.md files with embedded test plans for one user story at a time, ensuring all acceptance criteria are covered with BDD-style scenarios and coverage targets to prevent crashes and maintain quality.

Open repository

Best for

Primary workflow: Research & Ops.

Technical facets: Full Stack, Testing.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: anton-abyzov.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

  • Install test-aware-planner into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
  • Review https://github.com/anton-abyzov/specweave before adding test-aware-planner to shared team environments
  • Use test-aware-planner for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: test-aware-planner
description: Test-Aware Planning agent that generates tasks.md **ONE USER STORY AT A TIME** with embedded test plans. **CRITICAL CHUNKING RULE - Prevents crashes.** Activates for test planning, task generation with tests, BDD scenarios, coverage planning, and test-driven task breakdown. Keywords test-aware planning, chunked generation, BDD, Given-When-Then, test cases, coverage targets, embedded tests, tasks.md generation, test strategy, unit tests, integration tests, E2E tests, testable acceptance criteria.
allowed-tools: Read, Write, Grep, Glob, Edit
---

# Test-Aware Planner Skill

## Overview

You generate `tasks.md` with embedded test plans for each task. No separate tests.md - tests are inline with tasks.

## Progressive Disclosure

Load phases as needed:

| Phase | When to Load | File |
|-------|--------------|------|
| Spec Analysis | Reading spec.md/plan.md | `phases/01-spec-analysis.md` |
| Task Generation | Creating tasks | `phases/02-task-generation.md` |
| Validation | Checking AC coverage | `phases/03-validation.md` |

## Core Principles

1. **ONE user story per response** - Never generate all tasks at once
2. **Embedded tests** - Test plans inline with tasks
3. **AC coverage** - Every AC-ID must be covered

## Quick Reference

### Task Format

```markdown
## User Story: US-001 - Title

**Linked ACs**: AC-US1-01, AC-US1-02
**Tasks**: X total, 0 completed

### T-001: Task Title

**User Story**: US-001
**Satisfies ACs**: AC-US1-01
**Status**: [ ] pending

**Test Plan**:
- **Given** precondition
- **When** action
- **Then** expected result

**Test Cases**:
1. **Unit**: `tests/unit/feature.test.ts`
   - testFeatureSuccess(): Description
   - **Coverage Target**: 90%

2. **Integration**: `tests/integration/flow.test.ts`
   - testFullFlow(): Description
   - **Coverage Target**: 85%

**Implementation**:
1. Create file
2. Implement function
3. Run tests
```

### Coverage Targets

| Code Type | Target |
|-----------|--------|
| Core logic | 90-95% |
| API endpoints | 85-90% |
| Utilities | 80-85% |
| Overall | 80-90% |

### Multi-Project Format

If umbrella.enabled in config:
```markdown
## Phase 1: Shared (sw-app-shared)

### User Story: US-SHARED-001 - Types
**Linked ACs**: AC-SHARED-US1-01
```

## Workflow

1. **Analysis** (< 500 tokens): List user stories, ask which first
2. **Generate ONE US tasks** (< 800 tokens): Write to tasks.md
3. **Report progress**: "US-001 complete. Ready for US-002?"
4. **Repeat**: One user story at a time

## Token Budget

- **Analysis**: 300-500 tokens
- **Each user story**: 600-800 tokens

**NEVER exceed 2000 tokens per response!**

## Validation Checklist

- [ ] All AC-IDs from spec.md covered
- [ ] Each testable task has Given/When/Then
- [ ] Coverage targets are 80-90%
- [ ] Tasks grouped by User Story
- [ ] Frontmatter has by_user_story map
test-aware-planner | SkillHub