plan-guideline

Generate implementation plans with file modifications, LOC estimates, and Docs-then-Tests-then-Code workflow.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ayazhankadessova/essential-skills --skill plan-guideline-ayazhankadessova
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-guideline
Source: https://github.com/ayazhankadessova/essential-skills/tree/main/plugins/essential-skills/skills/plan-guideline
Command: npx skills add https://github.com/ayazhankadessova/essential-skills --skill plan-guideline-ayazhankadessova

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers create detailed, structured, and actionable implementation plans for software development tasks, ensuring clarity and efficiency.

Core Features & Use Cases

  • Structured Planning: Generates plans with specific file names, line ranges, and LOC estimates.
  • Workflow Enforcement: Mandates a Docs-then-Tests-then-Code order for implementation steps.
  • Use Case: When starting a new feature, use this Skill to outline exactly which files need modification, what new tests to write, and the order of operations, preventing scope creep and ensuring thoroughness.

Quick Start

Use the plan-guideline skill to create a detailed implementation plan for adding user authentication to the application.

Frequently Asked Questions about plan-guideline

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

FAQPage Schema
How do I create an actionable implementation plan for a new software feature?

To create an implementation plan, generate a blueprint specifying exact file modifications, line ranges, and Lines of Code (LOC) estimates. This enforces a strict Docs-then-Tests-then-Code workflow, ensuring structured development and preventing scope creep.

What is the Docs-then-Tests-then-Code workflow in software development planning?

The Docs-then-Tests-Tests-then-Code workflow is a mandated sequence for implementation steps. It requires finalizing documentation, writing tests, and then writing the actual code, ensuring thoroughness and adherence to best practices during feature refactors or bug fixes.

How do I estimate code complexity for a refactoring task?

Estimate code complexity for refactoring tasks using Lines of Code (LOC) metrics. By specifying file modifications and line ranges in your implementation plan, you can accurately gauge the scale of the work and allocate engineering resources efficiently.

Can I use this structured planning approach for both bug fixes and new features?

Yes, this structured planning approach works for bug fixes, feature development, and refactors. It generates detailed blueprints with specific file names and line ranges, ensuring clarity and efficiency across any software development task.

What is the best way to prevent scope creep when starting a new software project?

The best way to prevent scope creep is to build a detailed implementation plan outlining exactly which files need modification and what new tests to write. Mandating a strict Docs-then-Tests-then-Code order ensures thoroughness and boundary enforcement.