writing-plans

Generate detailed implementation plans with code, testing, and commit instructions.

4|1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/alixex/aryxn --skill writing-plans-alixex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/alixex/aryxn/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/alixex/aryxn --skill writing-plans-alixex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill generates comprehensive, step-by-step implementation plans for software development tasks, ensuring clarity and reducing ambiguity for engineers.

Core Features & Use Cases

  • Detailed Task Breakdown: Creates bite-sized, actionable tasks for developers.
  • Contextual Information: Includes necessary file paths, code snippets, testing instructions, and commit messages.
  • Use Case: Before starting a new feature, use this Skill to generate a detailed plan that outlines every code change, test, and documentation update required, ensuring a smooth development process.

Quick Start

Use the writing-plans skill to generate an implementation plan for adding user authentication.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate an implementation plan for a multi-step software development task?

To generate an implementation plan, you define the multi-step software development task, and the skill outputs granular, actionable steps including exact file paths, code snippets, and execution commands for engineers.

Does the generated implementation plan include testing and commit instructions?

Yes, the generated implementation plan includes specific testing instructions and commit messages, ensuring adherence to TDD, YAGNI, and DRY principles alongside the required code snippets.

What is the best way to break down feature development into actionable tasks for engineers?

The best way to break down feature development is to generate a detailed task breakdown that provides bite-sized, contextual steps with necessary file paths, code snippets, and documentation updates.

Can I use this for planning code generation and documentation updates simultaneously?

Yes, you can use this for planning code generation and documentation updates simultaneously, as it outlines every code change, test, and documentation update required for a smooth development process.

When do I need a detailed task breakdown for software development?

You need a detailed task breakdown for software development when starting a new feature or facing limited context, ensuring clarity and reducing ambiguity by specifying exact execution commands and code.