Lfe to Issues

Break the PRD into independently-demoable vertical slice issues. Use in the Architect sub-pipeline after to-prd completes. Requires human approval of slices.

44 stars 3 forksOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add StChiotis/Library-First-Engineering --skill lfe-to-issues
Manual install
git clone --depth 1 https://github.com/StChiotis/Library-First-Engineering.git /tmp/Library-First-Engineering
mkdir -p ~/.claude/skills
cp -r /tmp/Library-First-Engineering/.agents/skills/lfe-to-issues ~/.claude/skills/lfe-to-issues

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# LFE To Issues

## Position in Pipeline
- **Phase**: 1 (Architect sub-pipeline, Step 3)
- **Persona**: Architect
- **Input**: `.plans/02_prd.md`
- **Output**: `.plans/03_slices.md`
- **Gate**: 🛑 Human must approve slices before proceeding

## Process

### 1. Read input
Read `.plans/02_prd.md` as the source of truth — it carries this step's inputs, not the conversation.

### 2. Draft vertical slices
Break the PRD into **tracer bullet** slices. Each slice is a thin vertical cut through ALL integration layers end-to-end, NOT a horizontal slice of one layer.

Slices are either:
- **AFK** — can be implemented and merged without human interaction
- **HITL** — requires a human decision, design review, or external dependency

Prefer AFK over HITL where possible.

**Vertical slice rules:**
- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
- A completed slice is demoable or verifiable on its own
- Prefer many thin slices over few thick ones

### 3. Present to human
Present the proposed breakdown as a numbered list. For each slice show:

- **Title**: short descriptive name
- **Type**: HITL / AFK
- **Blocked by**: which other slices must complete first
- **User stories covered**: which user stories this addresses

Ask the human:
- Does the granularity feel right?
- Are the dependency relationships correct?
- Should any slices be merged or split further?
- Are the correct slices marked as HITL and AFK?
Read the full skill on GitHub

Details

Skill name
lfe-to-issues
Path
.agents/skills/lfe-to-issues/SKILL.md
License
MIT
Repo updated
14 July 2026

FAQ

What does the Lfe to Issues skill do?

Break the PRD into independently-demoable vertical slice issues. Use in the Architect sub-pipeline after to-prd completes. Requires human approval of slices.

How do I install the Lfe to Issues skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add StChiotis/Library-First-Engineering --skill lfe-to-issues. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Lfe to Issues popular?

It lives in StChiotis/Library-First-Engineering, which has 44 GitHub stars and 3 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.