skills.rest
huynguyenh
huynguyenhCOMMUNITY
Explore all skills by this author →
GitHub

hnh-wbs

Generate CTO-level Work Breakdown Structures for software projects as branded PDFs.

3|Updated Mar 9, 2026
Search Tags:#software development#project planning#estimation#pdf generation#feasibility analysis#wbs#technical scope
One-click install
npx skills add https://github.com/huynguyenh/skills --skill hnh-wbs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hnh-wbs
Source: https://github.com/huynguyenh/skills/tree/main/skills/hnh-wbs
Command: npx skills add https://github.com/huynguyenh/skills --skill hnh-wbs

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of comprehensive Work Breakdown Structures (WBS) for software projects, transforming project briefs into detailed, actionable plans.

Core Features & Use Cases

  • Generate WBS PDFs: Creates branded, module-level WBS documents covering all SDLC stages.
  • Evaluate Technical Approaches: Analyzes multiple technical solutions and their tradeoffs.
  • Assess Technical Feasibility: Identifies risks and challenges in project requirements.
  • Scope & Estimate Projects: Can operate in scope-only mode or provide detailed man-day estimates and timelines.
  • Use Case: A startup founder has a new app idea and needs a clear development roadmap, including technical feasibility, architectural choices, and a phased plan with estimated effort.

Quick Start

Generate a CTO-level Work Breakdown Structure (WBS) for a new software project based on the provided brief.

Frequently Asked Questions about hnh-wbs

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

FAQPage Schema
How do I generate a Work Breakdown Structure for a software project?▼

To generate a Work Breakdown Structure, provide a project brief and the system will create a module-level WBS covering all SDLC stages, evaluating technical approaches and delivering a branded PDF.

What is a CTO-level WBS and how does it handle technical feasibility analysis?▼

A CTO-level WBS is a comprehensive project plan that breaks down software development into modules while assessing technical feasibility by identifying risks, evaluating multiple technical approaches, and detailing their tradeoffs.

Can I get man-day estimates and timelines from a project brief?▼

Yes, you can get man-day estimates and timelines from a project brief by operating the system outside of its scope-only mode, allowing it to calculate detailed effort projections and schedules.

What formats of project briefs work for generating a WBS PDF?▼

The system handles project briefs in various formats to generate a WBS PDF, transforming the provided app idea or requirement document into a detailed, actionable development plan.

Does the WBS include technical scope and architectural choices for software development?▼

Yes, the WBS includes the technical scope and architectural choices by analyzing multiple technical solutions, evaluating their tradeoffs, and outlining a phased development plan for the software project.

Related Skills

Explore More Product & Management Skills→
cshyangcshyang

gsd:workflow:discovery-phase

Plan and execute a project discovery phase to define requirements and scope.

Community
Intermediate
infinith4infinith4
1

pm-schedule

Generate Gantt charts, milestones, and timelines from a WBS.

Community
Advanced
phant-appphant-app

interview

Conduct structured technical interviews to refine implementation plans.

Official
Intermediate
yodakeisukeyodakeisuke

Example Mapping Skill

Convert ambiguous requirements into executable acceptance criteria with Gherkin scripts.

Community
Basic