task-plan-writing

Write implementation plans with problem statements, alternatives, and justifications.

1|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/Anveio/conveaux --skill task-plan-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-plan-writing
Source: https://github.com/Anveio/conveaux/tree/main/.claude/skills/task-plan-writing
Command: npx skills add https://github.com/Anveio/conveaux --skill task-plan-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill elevates planning quality by framing implementation plans as if presenting to distinguished engineers.

Core Features & Use Cases

  • Distinguished Review: Automatically calibrate plans to survive scrutiny from domain experts.

Core Features & Use Cases

  • Rigorous Planning: Create plans that would satisfy technical steering committees.
  • Use Case: When entering plan mode or designing architecture, this Skill ensures your plans meet the highest standards of technical excellence.

Quick Start

When you need to plan a feature or architecture change, invoke this Skill to produce implementation plans of distinguished quality.

Quick Start

Use this Skill when designing new features to ensure your implementation strategy is sound and well-documented.

Quick Start

Invoke this Skill when the user asks to plan a feature or when you're entering plan mode.

Frequently Asked Questions about task-plan-writing

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

FAQPage Schema
How do I write implementation plans that satisfy technical steering committees?

Implementation plans need rigorous structure: problem statement, viable alternatives with justification, and architecture decisions aligned with hexagonal patterns. This Skill generates plans calibrated for distinguished engineers' scrutiny, ensuring your design choices survive expert review and meet decision-quality standards.

What should a high-quality architecture plan include?

Architecture plans must define the problem clearly, enumerate trade-offs between approaches, justify your choice, and document port/contract discipline. This Skill produces plans that frame implementation strategy for technical audiences, covering both what you're building and why that approach is sound.

When should I use rigorous planning versus quick sketches?

Use rigorous planning when entering formal design phases, presenting to domain experts, or making architectural commitments. Quick sketches work for exploration; this Skill applies when you need distinguished-quality output—plans that withstand scrutiny and document decisions for steering committees or senior engineers.

How do I frame a feature plan for technical leadership review?

Frame plans with explicit problem statements, alternative solutions you considered, and reasoned justification for your choice. This Skill structures implementation plans to survive distinguished engineer review by emphasizing decision rationale and architectural alignment, not just execution steps.

Can I use this for both feature planning and architecture design?

Yes. This Skill applies across plan mode—whether designing new features or system architecture. It ensures plans meet the same rigor: problem clarity, alternative analysis, and justified decisions that satisfy hexagonal architecture discipline and audience expectations for technical excellence.