doc-iplan

Converts TASKS into session-based bash command sequences for IPLAN workflows.

16|3|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-iplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-iplan
Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-iplan
Command: npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-iplan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates Implementation Plans (IPLAN) at Layer 12 by converting TASKS into session-based, executable bash command sequences for implementation.

Core Features & Use Cases

  • Session-based Execution Plan: Transforms TASKS into organized sessions with concrete commands.
  • Deterministic Commands: Provides repeatable, testable steps for implementation.
  • Dependencies & Verification: Includes task dependencies and verification checkpoints for each session.

Quick Start

Use doc-iplan after TASKS (Layer 11) to convert the task list into a runnable, session-based plan (IPLAN-XX_*.md) that can drive a hands-on implementation session.

Frequently Asked Questions about doc-iplan

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

FAQPage Schema
How do I convert a task list into executable bash commands?

Convert tasks into executable bash commands by organizing them into session-based sequences with concrete steps, dependencies, and verification checkpoints. This creates a runnable implementation plan that tracks each command's purpose and validates execution at each stage.

What's the best way to structure an implementation plan for team execution?

Structure implementation plans as session-based bash command sequences with frontmatter metadata, IPLAN naming conventions, tag-based traceability, and rollback procedures. This ensures repeatable, testable steps that teams can execute deterministically across multiple sessions.

How do I add verification and rollback steps to a bash execution plan?

Add verification checkpoints after each session to validate command outcomes and include rollback procedures that undo changes if verification fails. This supports traceability and safe re-execution if issues arise during implementation.

Can I use this for converting high-level task breakdowns into runnable scripts?

Yes. This Skill transforms task breakdowns from planning layers into session-by-session bash command sequences with sample commands and validation scripts, making abstract tasks concrete and executable for hands-on implementation.

What input format do I need before creating an execution plan?

Provide a structured task list with clear breakdowns, dependencies between tasks, and acceptance criteria. The Skill converts these tasks into session-based bash sequences with deterministic commands that satisfy your implementation and validation requirements.

Why use session-based execution instead of a single bash script?

Session-based execution organizes complex implementations into logical stages with verification between sessions, improving traceability, enabling checkpoint recovery, and supporting team hand-offs when tasks span multiple time blocks or participants.