pre-dev-subtask-creation

Generate bite-sized TDD subtasks with complete code and verification commands.

205|26|Updated Oct 30, 2025

Search Tags:#automation #planning #TDD #zero-context #subtask

Ready to run

npx skills add https://github.com/LerianStudio/ring --skill pre-dev-subtask-creation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pre-dev-subtask-creation
Source: https://github.com/LerianStudio/ring/tree/main/pm-team/skills/pre-dev-subtask-creation
Command: npx skills add https://github.com/LerianStudio/ring --skill pre-dev-subtask-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate 8: Zero-context implementation steps - 2-5 minute atomic subtasks with complete code, exact commands, TDD pattern. Large Track only.

Core Features & Use Cases

Atomic 2-5 minute steps with complete code and commands
TDD-driven subtask creation with explicit verification
DRY, YAGNI, and frequent commits

Quick Start

Create 2-5 minute subtasks saved to docs/pre-dev/{feature-name}/subtasks with full context and verification steps.

Frequently Asked Questions about pre-dev-subtask-creation

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

FAQPage Schema

How do I break down large features into atomic subtasks for development?▼

Atomize features into 2-5 minute subtasks with complete code, exact commands, and TDD verification steps. Each subtask includes full implementation, test commands, and rollback procedures, eliminating context-switching and enabling zero-context developers to execute independently.

What is a zero-context subtask and why does it matter?▼

A zero-context subtask is a self-contained 2-5 minute step with complete code, exact commands, and verification—no external knowledge required. It enables any engineer to implement features without understanding the broader codebase, reducing onboarding friction and accelerating large-track delivery.

How do I apply TDD discipline when planning implementation steps?▼

Structure each subtask in RED-GREEN-REFACTOR order: write failing tests first, implement code to pass, then refactor. Each subtask includes explicit test commands and verification steps, enforcing TDD discipline and guaranteeing testability before code ships.

Can I use subtask automation for pre-development planning before Gate 7 validation?▼

No. Subtask creation applies to large-track features after Gate 7 validation passes. Pre-development subtasks require validated requirements, architectural decisions, and explicit feature scope; use this for implementation planning, not requirements gathering.

What output format do atomic subtasks follow?▼

Subtasks are saved to docs/pre-dev/{feature-name}/subtasks with complete code, file paths, exact verification commands, TDD test patterns, and commit boundaries. Each step is self-contained and executable in 2-5 minutes with no external context needed.

How do I ensure subtasks follow DRY and YAGNI principles?▼

Each subtask avoids duplicating logic from prior steps and implements only features required by the current step—no speculative abstractions. Frequent commits after each subtask maintain rollback safety and prevent scope creep within atomic boundaries.