agent-sop-codetask

Generate structured code-task files from descriptions or PDD plans.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/japurcell/skills --skill agent-sop-codetask
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-sop-codetask
Source: https://github.com/japurcell/skills/tree/main/skills/agent-sop-codetask
Command: npx skills add https://github.com/japurcell/skills --skill agent-sop-codetask

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of turning rough descriptions or PDD implementation plans into structured code task files, enabling consistent task generation and governance.

Core Features & Use Cases

  • Converts high-level descriptions or PDD plans into a sequence of code-task articles that follow the Code Task Format.
  • Supports both description-driven and plan-driven workflows, preserving step dependencies and integration notes.
  • Facilitates planning, task breakdown, and artifact creation for software engineering teams to accelerate onboarding and iteration.

Quick Start

Generate a task breakdown from a provided description or PDD plan and export a ready-to-run code-task draft.

Frequently Asked Questions about agent-sop-codetask

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

FAQPage Schema
How do I generate structured code tasks from rough software engineering descriptions?

This Skill automates the generation of structured code-task files from rough descriptions or PDD plans. It ensures formal task artifacts are created with required frontmatter fields, kebab-case task naming, acceptance criteria, dependencies, and step-based creation according to the Code Task Format.

What is the best way to break down a PDD implementation plan into development tasks?

The best way to break down a PDD implementation plan is to automate the conversion into a sequence of code-task articles following the Code Task Format. This preserves step dependencies and integration notes while ensuring formal task artifacts are generated consistently.

Do I need a specific format to create code tasks with acceptance criteria and dependencies?

Yes, you need a format that enforces frontmatter fields, kebab-case task naming, acceptance criteria, dependencies, and step-based task creation. This Skill applies the Code Task Format to ensure your software engineering planning generates compliant formal task artifacts.

Can I automate task breakdown workflows for software engineering teams from high-level ideas?

You can automate task breakdown workflows by converting high-level ideas or PDD plans into a sequence of code-task articles. This facilitates planning and artifact creation for software engineering teams, accelerating onboarding and iteration through description-driven or plan-driven workflows.

What are the limitations of automating code-task generation from rough descriptions?

Automating code-task generation is limited to producing artifacts that follow the Code Task Format. It requires either a description-driven or plan-driven input and focuses on generating frontmatter, acceptance criteria, and dependencies, rather than executing the code tasks themselves.