loop-planner

Transform track specifications into plan.md files with tasks, criteria, and dependencies.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill loop-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-planner
Source: https://github.com/AhmedElhadarey/Gilfoyle/tree/main/skills/loop-planner
Command: npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill loop-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms track specifications into actionable execution plans, enabling teams to convert high-level requirements into a concrete, testable plan.

Core Features & Use Cases

  • Reads track spec.md and conductor context to produce a structured plan.md with tasks, acceptance criteria, and dependencies.
  • Performs DAG-based planning to identify parallelizable work and dependencies for deterministic execution.
  • Updates planning metadata and emits a ready-to-execute plan for handoff to the evaluator.

Quick Start

Load the current track's spec.md and context to generate a phased plan.md with explicit tasks, acceptance criteria, and dependencies.

Frequently Asked Questions about loop-planner

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

FAQPage Schema
How do I turn a vague spec into an actionable execution plan?

To turn a vague spec into an actionable execution plan, load your track's spec.md and context to generate a structured plan.md with explicit tasks, acceptance criteria, and dependencies for deterministic execution.

What is DAG-based planning for feature development?

DAG-based planning identifies parallelizable work and task dependencies from your specifications to create a deterministic execution plan, ensuring structured and traceable progress for new feature development.

How do I generate a plan.md with tasks and acceptance criteria?

Generate a plan.md with tasks and acceptance criteria by loading your track specification and context, which automatically composes a structured plan and records checkpoints in metadata for traceability.

Can I track execution dependencies for parallelizable work?

Yes, you can track execution dependencies for parallelizable work by applying DAG-based planning to your track specifications, which maps out task dependencies to enable deterministic execution and traceability.

Does converting track specifications into execution plans require external dependencies?

Converting track specifications into execution plans requires no external dependencies, operating directly on your loaded spec.md and context to produce the structured plan and metadata records.

When should I not use DAG-based planning for track specifications?

You should avoid DAG-based planning for track specifications when starting new tracks or features that lack defined context, as the system requires loaded specifications to compose tasks, acceptance criteria, and dependencies.