plan-epic

Generate TDD test suites and implementation plans for epics with pytest.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/lenlla/one_shot_build --skill plan-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-epic
Source: https://github.com/lenlla/one_shot_build/tree/main/skills/plan-epic
Command: npx skills add https://github.com/lenlla/one_shot_build --skill plan-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes ad-hoc planning and brittle development by ensuring tests are written first and remain immutable during the build, enabling predictable, reviewable, and repeatable epic implementations.

Core Features & Use Cases

  • TDD-first planning: Author complete failing tests for each step of an epic before any implementation.
  • Orchestrated workflow: Automate branch creation, git tagging, test execution, and plan file generation for agent-driven builds.
  • Use Case: When executing a single epic as part of an agentic CI-like build, use this Skill to produce precise test files under kyros-agent-workflow/tests, verify failures with pytest, tag the baseline, and write a step-by-step implementation plan to the build directory.

Quick Start

Invoke the execute-plan orchestrator with epic_spec_path pointing to the epic YAML, build_dir set to the target build directory, and epic_name set to the epic identifier to generate tests and an implementation plan.

Frequently Asked Questions about plan-epic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate TDD test suites before writing implementation code?

You can generate TDD test suites by authoring failing tests for each epic step before implementation. This Skill automates test file creation under the tests directory and verifies failures with pytest to establish a baseline.

What is TDD-first epic planning in an automated build workflow?

TDD-first epic planning is the process of writing complete failing tests for an entire epic before any implementation. It removes ad-hoc planning by enforcing test immutability, enabling repeatable agent-driven builds.

How do I automate git tagging and test execution for epic test baselines?

Automate git tagging and test execution by running the Skill as a subagent within an orchestrator. It executes pytest to confirm failing tests, tags the repository with a tdd-baseline identifier, and writes the plan file automatically.

Does this TDD planning approach work with pytest and git orchestration?

Yes, it works with pytest and git orchestration by operating as a subagent within orchestrators. The orchestrator supplies the epic spec path, build directory, and epic name to automate test generation, pytest execution, and git tagging.

When should I not use immutable test plans for epic implementation?

You should not use immutable test plans when your epic requires flexibility to change test expectations during implementation. The approach enforces test immutability throughout the build, which suits predictable CI-like workflows but limits adaptive test modification.