ac-decompose

Name: ac-decompose
Availability: InStock
Author: Pacvue

...

Updated Aug 27, 2026

Search Tags:#story #jira #subtasks #project-management #acceptance-criteria #decompose

Ready to run

npx skills add https://github.com/Pacvue/devflow-cursor --skill ac-decompose

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ac-decompose
Source: https://github.com/Pacvue/devflow-cursor/tree/main/.cursor/skills/ac-decompose
Command: npx skills add https://github.com/Pacvue/devflow-cursor --skill ac-decompose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Breaking down stories and tickets often leads to ambiguity and delays. This skill automatically converts requirements into clear Acceptance Criteria and actionable Sub-tasks, speeding up planning and alignment across teams.

Core Features & Use Cases

Detects Jira ticket IDs or natural language descriptions and routes to specialized subagents to derive structured work items.
Produces Acceptance Criteria in Given-When-Then format aligned with project conventions, and outputs a complete Sub-task breakdown with dependencies.
Integrates with the verifier subagent to ensure completeness before delivery and supports optional project conventions if available.

Quick Start

Provide a user story or Jira ticket to automatically generate acceptance criteria and subtasks.

Frequently Asked Questions about ac-decompose

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

FAQPage Schema

How do I automatically decompose Jira stories into acceptance criteria and subtasks?▼

You can automatically decompose Jira stories by providing the ticket ID to generate structured acceptance criteria and subtasks. The skill detects the Jira ticket and routes it to derive structured work items aligned with project conventions.

What is the Given-When-Then format for acceptance criteria in project management?▼

Given-When-Then is a structured acceptance criteria format used to define story requirements clearly. This skill enforces the Given-When-Then format for acceptance criteria to ensure completeness and align with project conventions.

Can I use natural language descriptions to generate subtasks and acceptance criteria?▼

Yes, you can use natural language descriptions to generate subtasks and acceptance criteria. The skill detects natural language inputs and routes them to specialized subagents to derive structured work items.

How do I ensure subtask breakdown completeness before delivery?▼

To ensure subtask breakdown completeness before delivery, the skill integrates with a verifier subagent. This verifier checks the generated acceptance criteria and subtasks to ensure completeness and alignment.

Does the subtask breakdown include dependencies for project management?▼

Yes, the subtask breakdown includes dependencies for project management. The skill outputs a complete subtask breakdown with dependencies to speed up planning and alignment across teams.

Do I need project conventions to decompose user stories into subtasks?▼

No, you do not need project conventions to decompose user stories, but the skill supports optional project conventions if available. It aligns the generated acceptance criteria and subtasks with these conventions when provided.