planning

Develop detailed implementation plans with phases, trade-offs, and security considerations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams transform vague requirements into concrete, maintainable technical plans, reducing ambiguity and rework while guiding stakeholders with clear roadmaps.

Core Features & Use Cases

  • Research & Analysis: Load diverse sources, identify feasible approaches, and document trade-offs.
  • Solution Design: Produce architecture and implementation design without writing code.
  • Plan Documentation: Create self-contained, actionable plans with milestones, risks, and acceptance criteria.

Quick Start

Ask the planning skill to produce a plan for a new feature: e.g., "Plan a scalable, secure authentication service with a phased rollout and documented trade-offs."

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create a detailed implementation plan for a new system feature?

Implementation planning transforms requirements into concrete technical plans by researching feasible approaches, analyzing your codebase, designing the solution architecture, and documenting phases with trade-offs, risks, and acceptance criteria. This reduces ambiguity and guides stakeholders through a clear roadmap.

What should a technical plan include for scalable and secure solutions?

A complete technical plan covers research findings, solution design, phased milestones, security and performance considerations, documented trade-offs between approaches, and acceptance criteria. Plans follow YAGNI, KISS, and DRY principles to ensure maintainability and clarity.

How do I document trade-offs when designing system architecture?

System architecture planning requires analyzing multiple feasible approaches, documenting the advantages and disadvantages of each, and justifying your chosen solution. Trade-off documentation provides stakeholders visibility into why specific technical decisions were made and what was rejected.

Can I use this for roadmap planning across multiple features?

Yes. Planning supports roadmap creation by producing self-contained, actionable plans for individual features that include phased rollout timelines, dependencies, and risk assessment. Multiple feature plans integrate into a cohesive technical roadmap.

What's the difference between solution design and implementation planning?

Solution design produces the architecture and detailed design without writing code, while implementation planning adds phased milestones, risks, acceptance criteria, and actionable steps. Together they create a complete blueprint for developers to execute.