writing-plans

Convert scattered design docs into an executable implementation plan with file changes.

9|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/iclinic/afyapowers --skill writing-plans-iclinic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/iclinic/afyapowers/tree/main/src/skills/writing-plans
Command: npx skills add https://github.com/iclinic/afyapowers --skill writing-plans-iclinic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning features in afyapowers often suffers from ambiguity when specs and designs are scattered across artifacts. The Writing Plans skill consolidates these inputs into a single, actionable implementation plan you can execute.

Core Features & Use Cases

  • Reads the active feature marker and design artifacts from the .afyapowers workspace and emits a structured plan.
  • Produces a plan detailing which files to touch, step-by-step tasks, testing, docs, and validation criteria.
  • Enforces modular task decomposition and scope checks to ensure testable, maintainable work units.

Quick Start

Announce at start: "I'm using the writing-plans skill to create the implementation plan."

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I convert scattered design specs into an executable implementation plan?

Implementation planning from specs consolidates scattered design docs into a single executable plan. It outputs a structured plan detailing file changes, step-by-step tasks, testing, docs, and validation criteria saved to artifacts/plan.md.

How do I generate a feature implementation plan with modular task decomposition?

Generate a feature implementation plan by applying modular task decomposition to enforce testable, maintainable work units. It enforces scope checks and outputs a structured plan detailing which files to touch, step-by-step tasks, and validation criteria.

What do I need to generate an implementation plan in the afyapowers workspace?

Generating an implementation plan requires an active feature marker and existing design artifacts in the .afyapowers workspace. The skill validates the current workflow phase is 'plan' before reading inputs and saving the resulting plan.

Can I use this plan generation skill if my workflow is not in the plan phase?

Plan generation fails if the workflow is not in the plan phase. The skill validates the active feature marker to ensure the current afyapowers workflow phase is 'plan' before reading design artifacts and saving the plan.

What is the best way to structure an executable plan from engineering design artifacts?

Structuring an executable plan from design artifacts requires enforcing proper structure and validation. This skill saves the resulting plan to artifacts/plan.md with step-by-step tasks, file changes, testing requirements, docs, and validation criteria.