skills.rest
AhmedElhadarey
AhmedElhadareyCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans with tasks, files, tests, and docs from a spec.

2|Updated Feb 25, 2026
Search Tags:#planning#documentation#implementation#specs#tests#task-breakdown
One-click install
npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill writing-plans-ahmedelhadarey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/AhmedElhadarey/Gilfoyle/tree/main/skills/writing-plans
Command: npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill writing-plans-ahmedelhadarey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating high-level specifications into a concrete, executable implementation plan that clarifies which files to touch, what tests to write, what docs to update, and how to structure commits.

Core Features & Use Cases

  • Generate end-to-end implementation plans from a spec, detailing required files, tests, documentation, and commit history.
  • Save plans to docs/plans/YYYY-MM-DD-<feature-name>.md to standardize project documentation.
  • Enforce best practices like DRY, TDD, and incremental commits, providing a repeatable workflow for software delivery.

Quick Start

Provide a feature spec and I will generate a complete implementation plan saved to docs/plans/YYYY-MM-DD-writing-plans.md.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn feature specs into executable implementation plans?▼

To turn feature specs into implementation plans, provide the high-level specification to generate a concrete document detailing required files, tests, documentation, and commit structure. The plan standardizes project workflow by enforcing DRY and TDD principles.

What is the best way to document task breakdowns for new software features?▼

The best way to document task breakdowns is generating a structured plan saved to docs/plans/YYYY-MM-DD-writing-plans.md. This enforces a fixed structure with explicit tasks, file touchpoints, and verification steps for repeatable software delivery.

How do I structure incremental commits using TDD for a new feature?▼

Incremental commits using TDD require a structured implementation plan detailing specific tests and file touchpoints. The plan enforces best practices like DRY and TDD, providing a repeatable workflow that clarifies commit history for new features.

Does this implementation plan generator require specific dependencies?▼

No, this implementation plan generator does not require specific dependencies or components. You simply provide a feature spec, and it outputs a standardized markdown plan enforcing DRY, TDD, and incremental commits without external tool constraints.

Can I use this to generate file touchpoints and verification steps for any project?▼

Yes, you can generate file touchpoints and verification steps for any software project. The tool applies the generated plan directly to your project and saves the result to docs/plans/YYYY-MM-DD-writing-plans.md, standardizing documentation across environments.

Related Skills

Explore More Software Engineering Skills→
Ibrahim-3dIbrahim-3d
371

writing-plans

Transform vague specifications into detailed implementation plans with file touchpoints and tests.

Community
Advanced
benjgradbenjgrad

writing-plans

Generate detailed implementation plans with tasks, files, tests, and commits.

Community
Advanced
VladlenFilimonovVladlenFilimonov

documentation

Standardize repository markdown documentation conventions and lifecycle management.

Community
Intermediate
BrmboboBrmbobo

writing-plans

Generate executable implementation plans from specs or requirements documents.

Community
Basic