Run any Skill in Manus with one click

to-issues

Decompose a plan, PRD, or spec into independently-grabbable vertical-slice issues (markdown file by default, GitHub issues via flag). Trigger when the user wants implementation tickets, work decomposition, or to convert an implementation plan into parallelizable work. Takes a plan file and emits atomic vertical slices.

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill to-issues

Copy and paste this command into Claude Code to install the skill

Source

OutlineDriven/odin-gemini-cli-extension

Stars5

Forks1

UpdatedMay 3, 2026 at 10:33

SKILL.md

readonly

name	to-issues
description	Decompose a plan, PRD, or spec into independently-grabbable vertical-slice issues (markdown file by default, GitHub issues via flag). Trigger when the user wants implementation tickets, work decomposition, or to convert an implementation plan into parallelizable work. Takes a plan file and emits atomic vertical slices.

Break a plan into tracer-bullet vertical slices. Each slice cuts end-to-end through every layer (schema, API, UI, tests) and is independently demoable. Reject horizontal layer-slices — they create blocked queues.

Emission Modes [LOCKED]

Default (file mode): Write to <project-root>/docs/issues/<feature>-slices.md as a numbered list of slices with the issue template per entry. Rerun-idempotent.

Flag mode (--emit-issue): After approval, create issues via gh issue create in dependency order so blocker references resolve to real numbers. Print URLs.

Process

1. Gather context

Read the source plan or PRD. If user passes a GitHub issue: gh issue view <number> --comments. If a plan file path: bat -P -p -n <path>. Otherwise work from active conversation.

2. Explore (if not already primed)

If the codebase is unfamiliar, dispatch an Explore agent. Trace integration layers: schema → service → API → UI → tests.

3. Draft vertical slices

Each slice MUST:

Cut through every relevant layer
Be demoable or verifiable on its own
Be either AFK (no human needed) or HITL (decision/review required) — prefer AFK
Be small enough that one engineer ships it in <2 days

Reject any slice that is "schema only" or "wire up later" — those are queue-blockers.

4. Quiz the user

Present the slate via a clarifying-question protocol. Show per slice: title, AFK/HITL, blocked-by references, user-stories covered. Ask: granularity correct? dependency edges correct? merge/split needed? AFK/HITL labels honest?

5. Emit

File mode: Write the approved slice list to docs/issues/<feature>-slices.md. Reference blockers by slice index. Commit.

Flag mode: gh issue create per slice in topological order. Capture each new issue number; backfill Blocked by with real numbers.

Issue Template

## Parent
#<parent-issue-number-or-PRD-path-or-omit>

## What to build
Concise end-to-end behavior description. Demoable outcome, not layer-by-layer mechanics.

## Acceptance criteria
- [ ] Observable criterion 1
- [ ] Observable criterion 2

## Blocked by
- #<issue-or-slice-number>   (or "None — start immediately")

## User stories covered
- US-1, US-3

Slice Examples Across Stacks

Rust + Postgres API: "Add GET /accounts/{id}/balance returning JSON; includes sqlx migration, handler, integration test against testcontainer Postgres." — one slice, all layers.
TypeScript + React frontend: "Render account balance with optimistic refresh; includes Zod response schema, TanStack Query hook, component, Vitest test." — one slice, all layers.
CLI tool (any language): "Add --dry-run flag to the migrate subcommand; includes flag parsing, no-op execution path, unit test." — one slice, all layers.

More from this repository

same repository

domain-model

OutlineDriven/odin-gemini-cli-extension

Grill against the existing domain model. Stress-test a plan's terminology against `CONTEXT.md` and ADRs; update both inline as decisions crystallise. Trigger when user proposes a feature/refactor that touches business concepts and the project has documented domain language to honor — or when domain language is missing and needs capture.

2026-05-045

write-a-skill

OutlineDriven/odin-gemini-cli-extension

Author a single new skill — produce a SKILL.md plus optional bundled references and scripts following Anthropic's progressive-disclosure conventions. Trigger when the user asks to "write a skill", "create a skill", "draft a SKILL.md", or "add a skill" for a specific capability. Distinct from repo onboarding workflows that write AGENTS.md and project conventions.

2026-05-045

triage-issue

OutlineDriven/odin-gemini-cli-extension

Investigate a reported bug to root cause, then emit a TDD-shaped fix plan as an issue artifact. Trigger when the user reports a bug, says "triage", asks for issue investigation, or wants a fix plan before code changes.

2026-05-035

ubiquitous-language

OutlineDriven/odin-gemini-cli-extension

Extract a domain glossary from the current dialogue; flag ambiguities, propose canonical terms, persist to `UBIQUITOUS_LANGUAGE.md`. Trigger when the user is hardening domain terminology, building a glossary, or fresh domain concepts surface in conversation without documented language.

2026-05-035

llm-self-loop

OutlineDriven/odin-gemini-cli-extension

Restructure Web-UI / human-triggered tasks into CLI + file-output loops the LLM can iterate alone. Open LLM-side observability — structured logs, file dumps, addressable scratchpads. Apply the trap-or-abandon decision: if a step cannot be looped, improve the harness rather than babysit. Trigger when the user mentions iterative grunt-work, "I have to push a button in a web UI to trigger this", monitoring dashboards, designing Claude-driven automation, or any workflow whose inner loop currently requires a human in the middle.

2026-04-295

ai-collab-protocols

OutlineDriven/odin-gemini-cli-extension

Surface concrete in-task-collaboration protocols when the user describes an AI workflow informally — URL-as-entity-reference, durable PR-comment threads as session memory, "fit the protocol" basics. Trigger when the user names entities by colloquial label instead of stable URL, asks "how should I structure this for Claude", pastes a screenshot when a URL would do, or describes a multi-step Claude workflow without a durable handle. Apply tactics reactively, not as a checklist.

2026-04-285

Source

OutlineDriven

OutlineDriven/odin-gemini-cli-extension

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Project Management SpecialistsBusiness and Financial Operations Occupations13-1082L4

name	to-issues
description	Decompose a plan, PRD, or spec into independently-grabbable vertical-slice issues (markdown file by default, GitHub issues via flag). Trigger when the user wants implementation tickets, work decomposition, or to convert an implementation plan into parallelizable work. Takes a plan file and emits atomic vertical slices.

Emission Modes [LOCKED]

Default (file mode): Write to <project-root>/docs/issues/<feature>-slices.md as a numbered list of slices with the issue template per entry. Rerun-idempotent.

Flag mode (--emit-issue): After approval, create issues via gh issue create in dependency order so blocker references resolve to real numbers. Print URLs.

Process

1. Gather context

Read the source plan or PRD. If user passes a GitHub issue: gh issue view <number> --comments. If a plan file path: bat -P -p -n <path>. Otherwise work from active conversation.

2. Explore (if not already primed)

If the codebase is unfamiliar, dispatch an Explore agent. Trace integration layers: schema → service → API → UI → tests.

3. Draft vertical slices

Each slice MUST:

Cut through every relevant layer
Be demoable or verifiable on its own
Be either AFK (no human needed) or HITL (decision/review required) — prefer AFK
Be small enough that one engineer ships it in <2 days

Reject any slice that is "schema only" or "wire up later" — those are queue-blockers.

4. Quiz the user

5. Emit

File mode: Write the approved slice list to docs/issues/<feature>-slices.md. Reference blockers by slice index. Commit.

Flag mode: gh issue create per slice in topological order. Capture each new issue number; backfill Blocked by with real numbers.

Issue Template

## Parent
#<parent-issue-number-or-PRD-path-or-omit>

## What to build
Concise end-to-end behavior description. Demoable outcome, not layer-by-layer mechanics.

## Acceptance criteria
- [ ] Observable criterion 1
- [ ] Observable criterion 2

## Blocked by
- #<issue-or-slice-number>   (or "None — start immediately")

## User stories covered
- US-1, US-3

Slice Examples Across Stacks

Rust + Postgres API: "Add GET /accounts/{id}/balance returning JSON; includes sqlx migration, handler, integration test against testcontainer Postgres." — one slice, all layers.
TypeScript + React frontend: "Render account balance with optimistic refresh; includes Zod response schema, TanStack Query hook, component, Vitest test." — one slice, all layers.
CLI tool (any language): "Add --dry-run flag to the migrate subcommand; includes flag parsing, no-op execution path, unit test." — one slice, all layers.