planning

Create structured technical roadmaps from ambiguous briefs to review-ready artifacts.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/dige04/hieu-ccsetup --skill planning-dige04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/dige04/hieu-ccsetup/tree/main/config/skills/planning
Command: npx skills add https://github.com/dige04/hieu-ccsetup --skill planning-dige04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning technical solutions is often manual, error-prone, and hard to scale; this skill provides a repeatable framework to produce high-quality plans that align with team capabilities and business goals.

Core Features & Use Cases

  • Structured research, analysis, and target-state design to inform decisions
  • Plan creation templates that standardize scope, risks, and milestones
  • Output-ready plan documents that can be handed to engineers, designers, and product managers
  • Use cases include feature planning, architecture reviews, and roadmapping for complex systems

Quick Start

Provide a complete planning plan outline for a new feature from a product brief.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create a technical roadmap from an ambiguous product brief?

Creating a technical roadmap from ambiguous briefs involves structured research, target-state design, and risk analysis to generate review-ready phase outputs. This enforces plan structure and documentation standards for repeatable architecture decisions.

What is the best way to standardize feature planning and architecture reviews for my engineering team?

Standardizing feature planning and architecture reviews uses plan creation templates to formalize scope, risks, and milestones. This produces output-ready plan documents that align team capabilities with business goals for engineers and product managers.

Can I use automated planning templates for complex systems architecture design?

Automated planning templates support complex systems architecture design by enforcing phase outputs and documentation standards. They transform ambiguous briefs into formal, review-ready roadmaps that standardize scope and ensure team alignment.

How does risk assessment integrate into technical planning for scalable solutions?

Risk assessment integrates into technical planning by applying structured analysis during target-state design to identify potential issues. This ensures scalable, end-to-end technical solutions include formal risk evaluation before generating review-ready artifacts.

Do I need prior documentation standards to generate actionable technical plans?

Prior documentation standards are not required to generate actionable technical plans. The framework enforces plan structure, phase outputs, and documentation standards automatically to ensure repeatable and maintainable planning work.