skills.rest
LightForgeLabsStudio
LightForgeLabsStudioOFFICIAL
Explore all skills by this author →
GitHub

plan

Create two-layer AIDE implementation plans from issue or pull request specifications.

2|Updated Dec 11, 2025
Search Tags:#workflow#planning#task management#github#implementation#aides
One-click install
npx skills add https://github.com/LightForgeLabsStudio/AIDE --skill plan-lightforgelabsstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/LightForgeLabsStudio/AIDE/tree/main/skills/plan
Command: npx skills add https://github.com/LightForgeLabsStudio/AIDE --skill plan-lightforgelabsstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed, two-layer implementation plans for software development tasks, ensuring alignment with project constraints and facilitating clear execution steps.

Core Features & Use Cases

  • Task Specification Input: Accepts issue/PR descriptions or numbers to define the scope.
  • Constraint Integration: Incorporates project-wide rules, invariants, and quality commands into the plan.
  • Layered Planning: Generates both high-level constraints and detailed, step-by-step implementation plans with exit criteria.
  • Use Case: A developer receives a new feature request as a GitHub issue. They use this Skill to generate a clear plan outlining the necessary code changes, testing strategies, and validation steps, ensuring all project standards are met before coding begins.

Quick Start

Use the plan skill to create a two-layer implementation plan from the text of issue number 123.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate an implementation plan from a GitHub issue?▼

To generate an implementation plan from a GitHub issue, input the issue or pull request specification. The system creates a two-layer plan, extracting project rules into Layer 1 Constraints and ordered steps with exit criteria into Layer 2.

What is a two-layer implementation plan for software development?▼

A two-layer implementation plan separates project-wide rules and invariants into Layer 1 Constraints, while Layer 2 contains ordered execution steps, file touchpoints, testing strategies, validation commands, and identified risks.

Does the plan workflow incorporate project constraints and testing strategies?▼

Yes, the plan workflow incorporates project constraints and testing strategies. It integrates project-wide rules into high-level constraints and details specific testing strategies alongside validation commands in the implementation steps.

Can I use issue numbers directly to define task scope for task management?▼

Yes, you can use issue or pull request numbers directly to define task scope. The system accepts issue or PR descriptions and numbers as task specifications to generate the structured implementation plan.

What are the limitations of automated implementation planning?▼

Automated implementation planning relies on the provided issue specification and known project rules. It generates structured steps and risks but cannot execute code changes, requiring developers to perform the actual implementation and validation.

Related Skills

Explore More Software Engineering Skills→
shiroinockshiroinock

tdd-next

Coordinate TDD task orchestration from GitHub issue selection to PR completion.

Community
Advanced
rezosndrezosnd

validation

Register and run named shell validation commands with per-command exit codes and logs.

Community
Intermediate
Reading-Advantage-ThailandReading-Advantage-Thailand

git-workflow

Orchestrate spec-driven development workflows with GitHub issues and pull requests.

Official
Advanced
royhenengelroyhenengel

plan

Generate spec-driven implementation plans for software development tasks.

Community
Intermediate