linear-slice

Solid

Decompose a plan into dependency-ordered Linear issues (tracer-bullet vertical slices) and release them into the autonomous dispatch pipeline.

AI & Automation 48 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
56
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /linear-slice Turn a plan or PRD into a set of **thin, vertical, independently-shippable slices**, each created as a Linear issue in dependency order, then released into Deus's autonomous dispatch pipeline. This is the missing front-end to the Linear pipeline: the webhook gates (`enrichment-gate` → `bouncer-gate` → dispatcher) describe how an issue *flows through* the board, but not how a good, independently-grabbable issue gets *created*. This skill creates them. Creating issues is a deliberate action with real side effects. **Always preview and get explicit approval before creating anything.** ## How the pipeline works (the contract you must honor) The board is `Backlog → Todo → Ready for Agent → Agent Working → In Review → Done`. Gates fire on **transitions into** a state, never on issue creation: - **Backlog → Todo** fires the **enrichment gate**, a *mutating* controller that writes the scope block into the issue description itself (wrapped in `<!-- gate:enrichment-gate:start -->` … `<!-- gate:enrichment-gate:end -->`). - **Todo → Ready for Agent** fires the **bouncer gate**, which validates that scope block. - The dispatcher then picks up `Ready for Agent` issues autonomously. Consequences for this skill: - **Create issues in Backlog.** A freshly created issue fires no gate, so it sits inert until moved. - **Never pre-write the enrichment scope block.** It is gate-owned. Write a normal human description; the enrichment gate generates the `## Scope` block ...

Details

Author
sliamh11
Repository
sliamh11/Deus
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

scaffold-sub-issues

Linear · Read one or more PLAN-*.md files and turn them into Linear sub-issues. Either creates a new parent issue from the plan (auto-detect mode) or adds sub-issues to an existing parent (when a parent ID is passed). Handles repo labels, blocks/blocked-by relations, and the manual-validation gate for /abc:ship-issue. Output is a parent ID you can paste into /abc:ship-issue or /abc:ship-epic. TRIGGER when the user says "/scaffold-sub-issues", "create Linear issues from this plan", "scaffold sub-issues for PARENT-ID", or passes a PLAN-*.md path.

0 Updated 1 weeks ago
semanticpixel
AI & Automation Solid

work-items-to-linear

Turn a work-items.md file (produced by /plan-work-items) into Linear issues, one per slice, in a single target Linear team. Use when you want to publish work items as Linear issues, create implementation tickets to track in Linear, or push a broken-down plan into a Linear team. Requires a configured Linear MCP server and a target team. Reads the team's real workflow states, labels, Projects, and members and resolves every option against them before creating anything; defaults each issue to the team's initial state, unassigned, uncategorized, with no parent or Project unless you ask. Links within-file `Depends on` relationships as native Linear "blocked by" relations and annotates the source file so re-runs resume cleanly. Does not produce the work-items file itself — use plan-work-items first. Does not post to Jira — use work-items-to-jira. Does not post to GitHub — use work-items-to-issues.

128 Updated today
testdouble
AI & Automation Listed

linear_breakdown

Break a large Linear issue into small, shippable tickets with clear scope, estimates, and dependencies.

2 Updated today
Tarekkharsa