task

Name: task
Availability: InStock
Author: cogni-dao

Decompose large work items into atomic PR-sized tasks with acceptance criteria.

14|Updated Jun 4, 2026

Search Tags:#acceptance criteria #task decomposition #workflow management #pr scope #engineering lead

Ready to run

npx skills add https://github.com/Cogni-DAO/node-template --skill task-cogni-dao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task
Source: https://github.com/Cogni-DAO/node-template/tree/main/.openclaw/skills/task
Command: npx skills add https://github.com/Cogni-DAO/node-template --skill task-cogni-dao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps engineering leads break down large roadmap items into manageable, PR-sized tasks, ensuring efficient development cycles and clear implementation guidance.

Core Features & Use Cases

Atomic Task Scoping: Defines precise boundaries for a single pull request.
Clear Acceptance Criteria: Establishes testable requirements for the implementing engineer.
Use Case: A product manager has a high-level feature request. The engineering lead uses this Skill to define the specific technical tasks, their IDs, and the acceptance criteria needed to implement that feature in a series of small, manageable pull requests.

Quick Start

Use the task skill to decompose the work for the new user authentication feature.

Frequently Asked Questions about task

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

FAQPage Schema

How do I decompose large roadmap items into PR-sized tasks?▼

You decompose work by breaking large features into atomic, PR-sized tasks with specific IDs, clear acceptance criteria, and scope boundaries to ensure efficient development cycles and implementation guidance.

What is the best way to define acceptance criteria for a single pull request?▼

Defining acceptance criteria for a single pull request involves establishing testable requirements and precise scope boundaries that the implementing engineer must meet before the task can be considered complete.

How does task decomposition work for engineering leads managing software development workflows?▼

Task decomposition works by taking high-level feature requests and dividing them into a series of small, manageable pull requests, each with a specific task ID and testable acceptance criteria for the implementing engineer.

Can I use this approach for high-level product manager feature requests?▼

Yes, engineering leads can use this task decomposition approach to translate a product manager's high-level feature request into specific technical tasks, IDs, and acceptance criteria needed for implementation.

Do I need specific templating rules for task decomposition and ID assignment?▼

Yes, task decomposition requires adherence to specific templating and ID assignment rules to maintain consistency across project management and software development workflows.

When should I not use atomic task scoping for workflow management?▼

Atomic task scoping may not suit work items that cannot be isolated into a single pull request or lack testable acceptance criteria, as it requires defining precise boundaries for manageable development units.