ai-dlc-blockers

Document AI-DLC session blockers with structured templates saved to blockers.md.

13|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/TheBushidoCollective/ai-dlc --skill ai-dlc-blockers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-dlc-blockers
Source: https://github.com/TheBushidoCollective/ai-dlc/tree/main/skills/ai-dlc-blockers
Command: npx skills add https://github.com/TheBushidoCollective/ai-dlc --skill ai-dlc-blockers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blockers stall AI-DLC sessions; proper documentation helps teams learn across iterations and keep momentum.

Core Features & Use Cases

  • Structured blocker documentation templates
  • Categorization (Technical, Knowledge, Dependency, Design)
  • Workflow integration with blockers.md saving and session progression
  • Enables knowledge transfer across hats (Builder, Reviewer, Planner)

Quick Start

Create a detailed blockers.md entry describing the current blocker and save it to blockers.md.

Frequently Asked Questions about ai-dlc-blockers

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

FAQPage Schema
How do I document blockers to preserve context across AI development lifecycle sessions?

You document blockers by creating structured templates that capture status, attempts, hypotheses, and next steps, saving entries directly to blockers.md to preserve context and learning across AI-DLC iterations.

What types of blockers should I track during AI-DLC workflows?

You should track Technical, Knowledge, Dependency, and Design blockers during AI-DLC workflows, categorizing each entry in blockers.md to guide resolution and facilitate knowledge transfer across Builder, Reviewer, and Planner hats.

How do I handle session handoff when an AI workflow blocker remains unresolved?

You handle session handoff by documenting the blocker's current status, attempted solutions, working hypotheses, and next steps in blockers.md, ensuring the next session or hat can resume work with full context.

What is the best way to structure blocker documentation for knowledge transfer?

The best way to structure blocker documentation is using templates that record the blocker type, status, failed attempts, hypotheses, and next steps, saving to blockers.md to accelerate AI-DLC work and maintain momentum.

Can I use blocker documentation across different roles within an AI-DLC workflow?

Yes, you can use blocker documentation across Builder, Reviewer, and Planner hats within any AI-DLC workflow, enabling knowledge transfer and session progression regardless of the role currently addressing the blocker.