loop-issues

Slice PRDs or plans into machine-checkable tracer-bullet issues via the loop workflow.

5|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/kenlck/skills --skill loop-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: loop-issues
Source: https://github.com/kenlck/skills/tree/main/ken-loop/skills/loop-issues
Command: npx skills add https://github.com/kenlck/skills --skill loop-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Slice a PRD or plan into independently-grabbable tracer-bullet issues with a machine-checkability gate, enabling automated governance and progress tracking across teams.

Core Features & Use Cases

  • Break PRDs into actionable tracer-bullet issues with acceptance criteria that are machine-checkable.
  • Publish through the loop workflow, labeling as AFK or HITL as appropriate and preserving traceability from PRD to each issue.
  • Use for turning plans into distributed, orchestrated work items that unattended agents can land.

Quick Start

Slice a PRD or plan into tracer-bullet issues ready for automated landing by an agent.

Frequently Asked Questions about loop-issues

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

FAQPage Schema
How do I turn a PRD into actionable tracer-bullet issues for automated agents?▼

To turn a PRD into tracer-bullet issues, you slice the plan into independently-grabbable work items equipped with machine-checkable acceptance criteria, enabling automated governance and distributed progress tracking across teams.

What are machine-checkable acceptance criteria in project management automation?▼

Machine-checkable acceptance criteria are explicit gate conditions and runnable checks attached to sliced PRD issues, allowing unattended agents to automatically verify non-change guarantees and prevent regressions without human intervention.

How do I slice a product plan into independently-grabbable issues for unattended agents?▼

Slicing a product plan requires breaking it into small, verifiable tracer-bullet slices and publishing them through the loop workflow, labeling each issue as AFK or HITL to direct autonomous or human-in-the-loop execution.

Do I need a specific framework to generate machine-checkable tracer issues from a PRD?▼

Yes, generating tracer issues requires the .loop/config.md framework to establish explicit gate criteria, runnable checks, and non-change guarantees to prevent regression and enable the loop workflow orchestration.

What is the difference between AFK and HITL labels in automated loop workflow orchestration?▼

AFK labels direct work items to unattended agents for autonomous execution, while HITL labels flag issues requiring human-in-the-loop intervention, preserving traceability from PRD to issue during the loop workflow distribution.