planning

Plan scalable technical solutions with implementation plans and trade-off analysis.

Updated Nov 12, 2025
One-click install
npx skills add https://github.com/thucpru/fontkit --skill planning-thucpru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/thucpru/fontkit/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/thucpru/fontkit --skill planning-thucpru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams design robust, scalable, and maintainable technical solutions, reducing risk and aligning with business goals.

Core Features & Use Cases

  • Structured planning: Create step-by-step implementation plans including research, design, and documentation.
  • Risk & trade-off assessment: Evaluate security, performance, and maintainability trade-offs before coding.
  • Reusable plan templates: Produce living documents that can be reused across projects and teams.

Quick Start

Provide a project brief or feature goal (e.g., "Plan a migration from a monolith to microservices for the checkout service, including milestones and acceptance criteria") and request a complete execution plan.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create a scalable architecture plan for a complex system?

Scalable architecture planning involves researching requirements, designing system components, evaluating trade-offs across performance and maintainability, and documenting implementation steps with acceptance criteria. This Skill structures that process end-to-end, producing actionable roadmaps that reduce risk before coding begins.

What should I document when planning a technical solution?

Technical solution documentation should include research findings, architectural decisions, security and performance trade-offs, implementation milestones, acceptance criteria, and step-by-step execution plans. This Skill generates self-contained docs that teams can reuse across projects.

How do I assess risks and trade-offs before implementing a feature?

Risk and trade-off assessment evaluates security implications, performance constraints, and maintainability costs of architectural choices. This Skill systematically analyzes these dimensions alongside requirements to surface hidden dependencies and help teams choose approaches aligned with business goals.

Can I use this for migration planning and feature scoping?

Yes. This Skill applies to both scenarios: feature scoping defines boundaries and acceptance criteria; migration planning structures phased rollouts with milestones and rollback contingencies. Both produce living documents with research, design rationale, and implementation steps.

What's the difference between planning and jumping straight to implementation?

Planning upfront surfaces architectural mismatches, security gaps, and scalability bottlenecks before costly rework. This Skill formalizes that discovery through structured research, design review, and trade-off documentation, reducing implementation delays and technical debt.

Do I need specific tools or templates to start planning?

No prerequisites beyond a project brief or feature goal. This Skill provides structured templates and reasoning to guide planning—you supply the context, and it produces step-by-step execution plans with documented trade-offs and acceptance criteria.