skills.rest
Wondersauce
WondersauceOFFICIAL
Explore all skills by this author →
WebsiteGitHub

ws-planner

Decompose development tasks into atomic sub-tasks with project documentation.

Updated Aug 23, 2026
Search Tags:#automation#planning#project management#development workflow#task decomposition#codebase documentation
One-click install
npx skills add https://github.com/Wondersauce/claude-code-plugin --skill ws-planner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ws-planner
Source: https://github.com/Wondersauce/claude-code-plugin/tree/main/skills/ws-planner
Command: npx skills add https://github.com/Wondersauce/claude-code-plugin --skill ws-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of breaking down development tasks into structured, actionable sub-tasks, ensuring adherence to project conventions and preventing architectural drift.

Core Features & Use Cases

  • Task Decomposition: Analyzes task descriptions and project documentation to create detailed, atomic sub-tasks.
  • Pattern Enforcement: Ensures all generated tasks follow documented playbooks, architectural patterns, and conventions.
  • Reuse Identification: Scans existing codebase documentation to identify and leverage reusable components, preventing duplication.
  • Use Case: When given a feature request like "Implement user authentication," ws-planner will break it down into specific tasks for backend API development, frontend UI implementation, and database schema updates, all while referencing existing patterns.

Quick Start

Use the ws-planner skill to plan the implementation of a new user profile page based on the project documentation.

Frequently Asked Questions about ws-planner

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

FAQPage Schema
How do I decompose development tasks into atomic sub-tasks?▼

Task decomposition breaks down development requests into specific, actionable sub-tasks by analyzing project documentation. This ensures all generated steps adhere to established architectural patterns, procedures, and conventions to prevent architectural drift.

How do I generate a development plan that enforces codebase conventions?▼

Generating a development plan with convention enforcement involves referencing project documentation to enforce established playbooks and architectural patterns. The process outputs structured sub-tasks that strictly align with your defined development lifecycle.

Can I identify code reuse opportunities when planning a feature implementation?▼

Yes, identifying code reuse opportunities involves scanning existing codebase documentation to leverage reusable components. This prevents duplication by ensuring generated sub-tasks for features like user authentication utilize established patterns before new development.

What is the best way to maintain development workflow consistency across complex features?▼

Maintaining development workflow consistency requires enforcing adherence to established architectural patterns and conventions during task decomposition. This method analyzes project documentation to prevent architectural drift across backend, frontend, and database tasks.

Does project management planning support session recovery for iterative development?▼

Yes, project management planning supports session recovery and re-planning with feedback for iterative development. It generates structured development plans that can be adjusted throughout the defined lifecycle as requirements evolve.

Why does architectural drift happen when implementing new user features?▼

Architectural drift happens when development tasks bypass documented playbooks and conventions. Preventing it requires decomposing tasks into atomic sub-tasks that reference existing codebase documentation to identify and leverage reusable components.

Related Skills

Explore More Software Engineering Skills→
rpelizzarpelizza

pelizzai-domain-modeling

Maps project-specific domain logic and architectural constraints for AI agents.

Community
Intermediate
GabeujinGabeujin

structured-autonomy-plan

Generate structured development plans with commit-level breakdowns for feature implementation.

Community
Intermediate
JmarquesJmarques

to-spec

Generate project specifications from codebase analysis and conversation context.

Community
Intermediate
januarfontijanuarfonti
10

task-generator

Generate task lists with sub-tasks and relevant files from specifications.

Community
Intermediate