hnh-plan

Generate principal-engineer-level implementation plans from plain text descriptions.

3|Updated Mar 9, 2026

Search Tags:#planning #architecture #software engineering #implementation #technical design #principal engineer

Ready to run

npx skills add https://github.com/huynguyenh/skills --skill hnh-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hnh-plan
Source: https://github.com/huynguyenh/skills/tree/main/skills/hnh-plan
Command: npx skills add https://github.com/huynguyenh/skills --skill hnh-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you create detailed, principal-engineer-level implementation plans for tasks, features, or bug fixes, ensuring thorough consideration of all technical aspects before development begins.

Core Features & Use Cases

Comprehensive Planning: Generates detailed plans covering system impact, database changes, API contracts, security, and testing strategies.
Risk Mitigation: Identifies potential issues and proposes solutions through parallel agentic investigation.
Use Case: You need to implement a new authentication flow. Use this Skill to generate a plan that details API changes, database migrations, security considerations, and a step-by-step implementation guide.

Quick Start

Use the hnh-plan skill to create a plan for refactoring the user profile service.

Frequently Asked Questions about hnh-plan

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

FAQPage Schema

How do I create a principal-engineer-level implementation plan from a plain text description?▼

To create a principal-engineer-level implementation plan from text, this Skill challenges the problem, interviews for clarity, and uses parallel agents to investigate context and architecture before writing a structured plan covering system impact, database changes, and security.

What is included in a comprehensive technical design plan for software engineering?▼

A comprehensive technical design plan includes detailed analysis of system impact, database changes, API contracts, performance considerations, security requirements, and step-by-step testing strategies generated through parallel agentic investigation.

How do I plan database migrations and API contract changes for a new feature?▼

Planning database migrations and API contract changes involves deep investigation into architecture and context, ensuring the final implementation plan thoroughly documents system impact, security considerations, and testing strategies before development begins.

Can I use this planning approach for both new features and bug fixes?▼

Yes, you can use this implementation planning approach for both new features and bug fixes. It generates detailed plans that ensure thorough consideration of all technical aspects, including system impact and testing strategies, before development begins.

What's the best way to identify potential risks and system impacts before coding?▼

The best way to identify risks and system impacts before coding is through parallel agentic investigation using Context Gatherer and Architecture Analyst agents, which propose solutions and ensure thorough consideration of performance, security, and testing strategies.

Do I need to provide a detailed technical specification to generate an architecture plan?▼

No, you do not need a detailed technical specification to generate an architecture plan. You can provide a plain text description or conversation context, and the Skill will interview for clarity and challenge the problem before writing the plan.