task

Plan code tasks with two rounds of design review and user approval.

121|3|Updated Jan 13, 2022
One-click install
npx skills add https://github.com/jiangzhe/doradb --skill task-jiangzhe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task
Source: https://github.com/jiangzhe/doradb/tree/main/.codex/skills/task
Command: npx skills add https://github.com/jiangzhe/doradb --skill task-jiangzhe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes task planning by enforcing deep research, multi-proposal design, formal review rounds, and explicit approvals before creating docs/tasks entries, reducing ambiguity and scope creep.

Core Features & Use Cases

  • Two-round design process: deep research, at least three proposals with tradeoffs, and two formal review rounds.
  • Explicit approval gate: require user consent before writing docs/tasks files and escalating to RFCs for oversized changes.
  • Broad applicability: suitable for planning features or bug fixes in large repos to align stakeholders and code impacts.

Quick Start

Initiate two-round design research to create and pre-approve a docs/tasks task document.

Frequently Asked Questions about task

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

FAQPage Schema
How do I plan a feature with multiple design proposals before creating docs/tasks entries?

Design task docs using a two-round process requiring deep background research, at least three design proposals with tradeoffs, and two formal review rounds before writing docs/tasks entries. Explicit user approval is enforced before any file creation.

What is the best way to handle scope creep when planning bug fixes in large code repositories?

Handle scope creep by enforcing an approval gate during task design that requires explicit user consent before writing docs/tasks files, and escalates oversized changes to RFCs for broader stakeholder alignment.

When do I need to escalate task planning to an RFC?

Escalate task planning to an RFC when the proposed feature or fix has an oversized scope that exceeds normal task boundaries, triggering the built-in RFC escalation process to align stakeholders.

How does the two-round design review process work for task planning?

The two-round design review process works by mandating deep background research first, then presenting at least three proposals with tradeoffs, followed by two formal review rounds to ensure rigorous evaluation before finalizing task docs.

Can I use this task design process for both new features and bug fixes?

Yes, you can use this task design process for planning both features and bug fixes within code repositories. It enforces background research, multi-proposal design, and formal reviews to reduce ambiguity across both scenarios.

Do I need explicit approval before writing docs/tasks files?

Yes, explicit user approval is required before writing docs/tasks files. The process acts as an approval gate to ensure all design proposals, tradeoffs, and formal review rounds are accepted before documentation begins.