skills.rest
juanca202
juanca202COMMUNITY
Explore all skills by this author →
Website𝕏@juanca202GitHub

work-plan

Plans technical tasks and maintenance work items as specification documents without writing code.

Updated May 8, 2026
Search Tags:#maintenance#user stories#task planning#technical specification#azure devops#spec-driven development#work items
One-click install
npx skills add https://github.com/juanca202/sdd-devkit --skill work-plan-juanca202
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-plan
Source: https://github.com/juanca202/sdd-devkit/tree/main/skills/work-plan
Command: npx skills add https://github.com/juanca202/sdd-devkit --skill work-plan-juanca202

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Turning a requirement or a maintenance need into a clear, agreed implementation plan is often skipped or done inconsistently, leading to ambiguous scope and duplicated work. This Skill produces structured planning documents — technical tasks (TK-XXX) under a user story, or self-contained maintenance work items (WI-XXX) — with acceptance criteria, dependencies, references, and implementation steps, without writing any code. ## Core Features & Use Cases - Two plan types: Creates TK-XXX technical tasks decomposed from an existing user story (covering its AC-XXX criteria), or WI-XXX maintenance work items for bugs, refactors, tech debt, dependency updates, and operational changes. - Stub or full plans: Reserves an ID with a minimal Draft stub, or produces a complete Ready-state plan with verifiable acceptance criteria, business rules, affected files, and an IT-XX implementation checklist. - Tracker integration: Optionally creates linked work items in Azure DevOps via MCP, using the external ID as the local task number and mirroring the full document into the work item fields. - Use Case: A user says "planifica US-007". The Skill reads the story, proposes a task decomposition grouped by repository covering every acceptance criterion, asks whether to create full plans or stubs, and hands off Ready tasks to implementation. ## Quick Start Ask the agent to plan the tasks for user story US-004, or to create a maintenance work item for a specific bug or refactor.

Frequently Asked Questions about work-plan

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

FAQPage Schema
How do I break a user story into technical tasks?▼

Provide only the story reference, such as "plan US-007". The Skill reads the story's acceptance criteria, proposes a task decomposition grouped by repository, and asks whether to create full plans or ID-reserving stubs before writing any files.

How do I plan maintenance work like a bug fix or refactor?▼

Describe the problem or scope and the Skill creates a WI-XXX work item: a single document combining description, acceptance criteria, dependencies, and an implementation plan. Large efforts are split into sibling work items, never sub-tasks.

Does work-plan integrate with Azure DevOps?▼

Yes, when project management integration is enabled in settings. It creates the work item via the Azure DevOps MCP server first, uses the returned ID as the local task number, and mirrors the full document into the work item description.

Can work-plan write code or run tests?▼

No. It only produces planning documents. Implementation is explicitly handed off to the work-implement skill, test cases to test-define, and architecture specifications to design-define via subagent delegation.

What happens if a task ID or scope already exists?▼

The Skill scans both active and archived spec folders before assigning IDs, since archived work keeps its identifier. On scope overlap with an existing task, it reports the conflict and asks whether to update the existing item or adjust the new one.

Related Skills

Explore More Software Engineering Skills→
Hassan-Ali-Mehdi-3024Hassan-Ali-Mehdi-3024

user-story-decomposition

Decompose features or PRDs into INVEST-compliant user stories with acceptance criteria.

Community
Advanced
jamesbondevjamesbondev

azure-devops-workflow

Manage Azure DevOps work item states, transitions, and branch naming conventions.

Community
Intermediate
TECH-HYTECH-HY

tpo-technical-specification-template

Generates structured technical specification documents from product requirements for developer agent execution.

Official
Intermediate
chohra-medchohra-med
28

spec-harness-tickets

Convert ticket tracker issues and ad-hoc plans into structured spec documents.

Community
Advanced