task-planner

Create implementation tasks with requirements and design traceability.

Updated Feb 1, 2026

Search Tags:#design #requirements #traceability #task-planning #engineering-workflow #feature-breakdown

Ready to run

npx skills add https://github.com/jralph/.config-opencode --skill task-planner-jralph

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-planner
Source: https://github.com/jralph/.config-opencode/tree/main/skills/task-planner
Command: npx skills add https://github.com/jralph/.config-opencode --skill task-planner-jralph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the creation of implementation tasks with complete traceability, linking each task to both requirements and design sections.

Core Features & Use Cases

Traceable Task Creation: Break features into atomic tasks that clearly reference the originating requirements and design sections.
Rule of Three: Enforce the 3-files-per-task constraint to prevent context overflow and improve maintainability.
Structured Task Format: Provide a template that includes Requirements references, Design references, and a clear top-level and subtasks structure.

Quick Start

To plan a feature, generate a set of atomic tasks that collectively cover all specified requirements and design sections, ensuring no task touches more than three files and each task includes Requirements: and Design: references.

Frequently Asked Questions about task-planner

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

FAQPage Schema

How do I break feature requirements into actionable engineering tasks?▼

Feature breakdown into actionable tasks requires generating atomic steps that each explicitly reference originating requirements and design sections. This traceability ensures all implementation work maintains clear links back to project specifications.

What is the Rule of 3 in task planning for software engineering?▼

The Rule of 3 in task planning is a constraint limiting each atomic task to touch a maximum of three files. This prevents developer context overflow and improves the overall maintainability of the engineering workflow.

How do I add requirements traceability to my development task list?▼

Requirements traceability is added to a task list by using a structured format with explicit Requirements and Design references for each item. This links every actionable subtask directly to its source specification sections.

Do I need existing design documents to generate a structured task format?▼

Yes, existing design documents and requirements are needed to generate a structured task format with traceability. The planning process references specific design sections and requirements to accurately map actionable steps back to original specifications.

What's the best way to prevent context overflow when planning engineering workflows?▼

The best way to prevent context overflow when planning engineering workflows is to enforce the Rule of 3, which limits each atomic task to modifying no more than three files. This constraint keeps individual implementation steps focused and manageable.