Agent skill

To Issues

Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe).

MITAuto-check passedProduct & Project Management

Install To Issues

skills CLI

$ npx skills add smallnest/pigo --skill to-issues -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install smallnest/pigo to-issues --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/smallnest/pigo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/internal/builtinskills/skills/to-issues .claude/skills/to-issues && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "to-issues" agent skill from https://github.com/smallnest/pigo/tree/master/internal/builtinskills/skills/to-issues into .claude/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/smallnest/pigo/tree/master/internal/builtinskills/skills/to-issues

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add smallnest/pigo --skill to-issues -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install smallnest/pigo to-issues --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/smallnest/pigo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/internal/builtinskills/skills/to-issues .agents/skills/to-issues && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "to-issues" agent skill from https://github.com/smallnest/pigo/tree/master/internal/builtinskills/skills/to-issues into .agents/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add smallnest/pigo --skill to-issues -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install smallnest/pigo to-issues --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/smallnest/pigo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/internal/builtinskills/skills/to-issues .cursor/skills/to-issues && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "to-issues" agent skill from https://github.com/smallnest/pigo/tree/master/internal/builtinskills/skills/to-issues into .cursor/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/smallnest/pigo.git --path internal/builtinskills/skills/to-issues

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add smallnest/pigo --skill to-issues -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install smallnest/pigo to-issues --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/smallnest/pigo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/internal/builtinskills/skills/to-issues .gemini/skills/to-issues && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "to-issues" agent skill from https://github.com/smallnest/pigo/tree/master/internal/builtinskills/skills/to-issues into .gemini/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install smallnest/pigo to-issues

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add smallnest/pigo --skill to-issues -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/smallnest/pigo.git skills-src && mkdir -p .github/skills && cp -r skills-src/internal/builtinskills/skills/to-issues .github/skills/to-issues && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "to-issues" agent skill from https://github.com/smallnest/pigo/tree/master/internal/builtinskills/skills/to-issues into .github/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add smallnest/pigo --skill to-issues -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install smallnest/pigo to-issues --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/smallnest/pigo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/internal/builtinskills/skills/to-issues .opencode/skills/to-issues && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "to-issues" agent skill from https://github.com/smallnest/pigo/tree/master/internal/builtinskills/skills/to-issues into .opencode/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: to-issues
GitHub stars: 475
Token cost: ~1.9k tokens
SKILL.md length: 570 words
Files: 1
Skills in repo: 2
Repo updated: Sep 13, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe).

Works in 5 steps: Locate Input → Decompose into Issues → Choose Creation Mode → …
: create issues
SKILL.md covers The Job, Step 1: Locate Input, Step 2: Decompose into Issues and Step 3: Choose Creation Mode, plus 4 more sections
Calls gh

What it does

To Issues is an agent skill from smallnest/pigo. Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe). Use after /prd (and optionally /prd-to-spec) to turn requirements into actionable tickets. Triggers on: create issues, to-issues, 创建issue, 拆解issue, 生成卡片, 创建卡片, generate issues from PRD, issues from spec.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing. It works with GitHub. The licence is MIT.

When your agent uses it

: create issues
Generate issues from PRD
Issues from spec

Example prompts

“/to-issues”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Locate Input
Decompose into Issues
Choose Creation Mode
Mode-Specific Creation
Summary Report

What it can do on your machine

Read from SKILL.md and the folder at commit 891d1f3. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

To Issues loads about 1.9k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 570 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~85
When it runs · the whole SKILL.md, loaded when a task matches: ~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from smallnest/pigo at commit 891d1f3, republished under its MIT licence (© smallnest). 570 words, ~1,854 tokens.

Download SKILL.mdSave it as .claude/skills/to-issues/SKILL.md (or your agent's skills folder).

name: to-issues
description: Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe). Use after /prd (and optionally /prd-to-spec) to turn requirements into actionable tickets. Triggers on: create issues, to-issues, 创建issue, 拆解issue, 生成卡片, 创建卡片, generate issues from PRD, issues from spec.
user-invocable: true

to-issues — PRD/SPEC to Issues

Decompose a PRD and/or technical SPEC into small, independent, implementable Issues, then create them in your chosen platform. Works standalone — you don't need to have run /prd first.

The Job

Locate input — find a PRD or SPEC file (auto-detect or user-specified)
Decompose into Issues — break User Stories into implementable tickets
Review with user — present Issue list for approval and adjustment
Choose platform — GitHub / Local / Baidu iCafe
Create Issues — create all tickets and print summary

Step 1: Locate Input

Find the input document:

What should I base the Issues on?

A. Auto-detect: scan tasks/ for recent PRDs and SPECs
B. Specific PRD file (e.g., tasks/prd-priority-system.md)
C. Specific SPEC file (e.g., tasks/spec-priority-system.md)
D. Both PRD and SPEC (best: PRD for requirements, SPEC for technical contracts)
E. Paste requirements directly

If auto-detecting, list available files and let the user choose.

If both PRD and SPEC are available, use the SPEC's Section 10.2 (Issue Mapping) as the primary guide, supplemented by PRD's User Stories. If only PRD is available, generate Issues directly from User Stories.

Step 2: Decompose into Issues

Based on the input document(s), generate a list of Issues. Follow these rules:

One Issue per User Story — each US-XXX becomes at least one Issue
Split large stories — if a US has 5+ acceptance criteria or spans frontend + backend, split into 2-3 smaller Issues with clear dependencies
Merge tiny stories — if a US has only 1-2 trivial criteria, merge it with a related US into a single Issue
Each Issue must be independently implementable — a single agent session should be able to complete it
Number Issues sequentially starting from 1
If SPEC is available — enrich Issues with SPEC references (API endpoints, data model sections, error handling contracts)

Issue format:

Issue #N: [Title]
---
Description: [From US description, with context]
Acceptance Criteria:
- [ ] [From US acceptance criteria]
- [ ] ...
Dependencies: [None / Issue #X]
Type: [backend / frontend / fullstack / ui / infra]
Priority: [high / medium / low]
SPEC Reference: [Section X.Y — only if SPEC available]

Present the Issue list for review:

📋 Generated N Issues from [PRD/SPEC]:

#1: Add priority field to database (backend, high)
#2: Display priority indicator on task cards (frontend, high) — depends on #1
#3: Add priority selector to task edit (frontend, medium) — depends on #1
#4: Filter tasks by priority (frontend, medium) — depends on #1, #2

Please review. You can:
- Remove issues: "remove #3"
- Merge issues: "merge #2 and #3"
- Add issues: "add an issue for sorting by priority"
- Adjust: "change #2 priority to high"
- Confirm: reply OK to proceed

Wait for user confirmation before creating any Issues.

Step 3: Choose Creation Mode

After user confirms the Issue list, ask:

Choose where to create these Issues:

A. GitHub (via gh CLI)
B. Local (save as .md files)
C. Baidu iCafe (via icafe-cli)

Your choice:

Step 4: Mode-Specific Creation

Mode A: GitHub

Prerequisites: gh CLI installed and authenticated.

Actions:

For each Issue, run:

bash

gh issue create --title "[Title]" --body "[Description + Acceptance Criteria]" --label "[type]" --label "priority: [priority]"

If labels don't exist, create them first or skip the --label flag
Report created Issue numbers and URLs

Mode B: Local

Ask user:

Where should I save the Issue files? (default: .autoresearch/issues)

Actions:

If the specified folder does not exist, create it with mkdir -p

For each Issue #N, save a file named issue-NNN-[slug].md (zero-padded to 3 digits):

markdown

# [Title]

## Description
[Description from Issue]

## Acceptance Criteria
- [ ] [criterion 1]
- [ ] [criterion 2]

## Dependencies
[None / Issue #X]

## Type
[backend / frontend / fullstack / ui / infra]

## Priority
[high / medium / low]

Report created file paths

Show full SKILL.md (232 more words)Show less

Mode C: Baidu iCafe

Ask user:

Please provide the iCafe space prefix code (--space):

Optionally ask:

Target branch for iCode CR? (default: master)

Prerequisites: icafe-cli installed and logged in.

Actions:

For each Issue, run:
bash
```
icafe-cli card create --space [SPACE] --title "[Title]" --description "[Description + Acceptance Criteria]" --cardtype "[Task/Bug/Story]"
```
- Map Issue type to iCafe card type: bug → Bug, ui/frontend → Story, others → Task
- Map priority: high → 高, medium → 中, low → 低
If iCafe card creation fails for an Issue, log the error and continue with remaining Issues
Report created card sequence numbers

Step 5: Summary Report

After all Issues are created, print a summary:

✅ Issue creation complete!

Source: [PRD/SEC path]
Mode: [GitHub / Local / Baidu iCafe]
Issues created: N

#  | Title                                    | Identifier
---|------------------------------------------|------------
1  | Add priority field to database           | #42 (GitHub) / issue-001-*.md (Local) / #22210 (iCafe)
2  | Display priority indicator               | #43 / issue-002-*.md / #22211
3  | Add priority selector                    | #44 / issue-003-*.md / #22212
4  | Filter tasks by priority                 | #45 / issue-004-*.md / #22213

💡 Tip: Now implement each Issue with /goal:
  /goal 42                    # GitHub mode
  /goal issue-001-*.md        # Local mode

Edge Cases & Fallback

Scenario	Handling
No PRD/SPEC found in tasks/	Ask user to provide file path or paste requirements
PRD has no User Stories	Derive Issues from Functional Requirements instead
SPEC has Issue Mapping (Section 10.2)	Use it as primary source, cross-reference with PRD
`gh` CLI not authenticated for GitHub mode	Show error, suggest `gh auth login`, offer to switch to Local mode
`icafe-cli` / `icode-cli` not installed for Baidu mode	Show error, suggest installation, offer to switch to Local mode
Issue folder does not exist for Local mode	Auto-create the folder
User declines Issue creation	Print the Issue list as a text summary, let user create manually later

Relationship to Other Skills

/prd  →  /prd-to-spec (optional)  →  /to-issues  →  /goal  →  /review-it  →  /ship-it
 │              │                        │              │
 │  Requirements │  Technical design     │  Tickets     │  Implementation
 │  (what)       │  (how)                │  (units)     │  (code)

/prd — produces the PRD (input to this skill)
/prd-to-spec — produces the SPEC (optional, enriches Issues with technical detail)
/to-issues — produces the Issues (this skill)
/goal — implements Issues one by one

Files

Just SKILL.md in internal/builtinskills/skills/to-issues of smallnest/pigo.

Open the folder on GitHubat commit 891d1f3

Compare with similar skills

To Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

To Issues compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
To Issues this skillsmallnest/pigo	475	—	~1.9k	Automated safety check: Pass	MIT	25 days ago
CCPM Project Managementautomazeio/ccpm	8.4k	—	~1.1k	Automated safety check: Pass	MIT	6 mo ago
Ouroboros PM InterviewQ00/ouroboros	6.2k	1 repos	~5.7k	Automated safety check: Pass	MIT	yesterday
Write A Prdbestofjs/bestofjs	3.1k	1 repos	~722	Automated safety check: Pass	MIT	4 days ago
Write Update Tidb Docspingcap/docs	616	—	~2.3k	Automated safety check: Pass	Custom licence	yesterday
Write Product Specbholmesdev/hubble.md	1.5k	—	~966	Automated safety check: Pass	MIT	6 days ago

Similar skills

CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
Product & Project ManagementAuto-check passed
Ouroboros PM Interview
Q00/ouroboros
Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.
6.2k GitHub starsUsed in 1 repo~5.7k tokens
Product & Project ManagementAuto-check passed
Write A Prd
bestofjs/bestofjs
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue.
3.1k GitHub starsUsed in 1 repo~722 tokens
Product & Project ManagementAuto-check passed
Write Update Tidb Docs
pingcap/docs
Write new TiDB documentation or update existing TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions.
616 GitHub stars~2.3k tokensUpdated yesterday
Product & Project ManagementAuto-check passed
Write Product Spec
bholmesdev/hubble.md
Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior.
1.5k GitHub stars~966 tokensUpdated 6 days ago
Product & Project ManagementAuto-check passed
Foreman To Issues
VisionForge-OU/foreman
Break an approved PRD into small, dependency-ordered, vertically-sliced implementation issues written as local files in the Foreman feature directory.
443 GitHub stars~1.2k tokensUpdated 3 mo ago
Product & Project ManagementAuto-check passed

Questions about To Issues

What does To Issues do?

Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe). To Issues is an agent skill from smallnest/pigo. Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe).

When should I use To Issues?

To Issues fits situations like: : create issues; generate issues from PRD; issues from spec.

How do I install To Issues in Claude Code?

Run `npx skills add smallnest/pigo --skill to-issues -a claude-code`. Or copy the skill folder (internal/builtinskills/skills/to-issues in smallnest/pigo) into .claude/skills/to-issues in your project. Claude Code loads it when a task matches its description.

How do I install To Issues in Codex?

Run `npx skills add smallnest/pigo --skill to-issues -a codex`. Or copy the skill folder (internal/builtinskills/skills/to-issues in smallnest/pigo) into .agents/skills/to-issues in your project. Codex loads it when a task matches its description.

Can I use To Issues in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add smallnest/pigo --skill to-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/to-issues, .gemini/skills/to-issues, .github/skills/to-issues and .opencode/skills/to-issues in your project.

What does To Issues need to run?

Going by SKILL.md and its folder, To Issues needs the command-line tools its instructions call (gh).

Does To Issues access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is To Issues safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does To Issues use?

To Issues is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does To Issues use?

About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to To Issues?

Skills that share tags, products or a category with To Issues: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ouroboros PM Interview (Q00/ouroboros, 6.2k stars), Write A Prd (bestofjs/bestofjs, 3.1k stars) and Write Update Tidb Docs (pingcap/docs, 616 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains To Issues?

smallnest (a GitHub user) maintains it in smallnest/pigo, which has 475 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 13, 2026.

Source: smallnest/pigo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

To Issues

Install To Issues

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

to-issues — PRD/SPEC to Issues

The Job

Step 1: Locate Input

Step 2: Decompose into Issues

Step 3: Choose Creation Mode

Step 4: Mode-Specific Creation

Mode A: GitHub

Mode B: Local

Mode C: Baidu iCafe

Step 5: Summary Report

Edge Cases & Fallback

Relationship to Other Skills

Files

Compare with similar skills

Similar skills

CCPM Project Management

Ouroboros PM Interview

Write A Prd

Write Update Tidb Docs

Write Product Spec

Foreman To Issues

More from smallnest/pigo

Architecture Diagram

Questions about To Issues

Install To Issues

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

to-issues — PRD/SPEC to Issues

The Job

Step 1: Locate Input

Step 2: Decompose into Issues

Step 3: Choose Creation Mode

Step 4: Mode-Specific Creation

Mode A: GitHub

Mode B: Local

Mode C: Baidu iCafe

Step 5: Summary Report

Edge Cases & Fallback

Relationship to Other Skills

Files

Compare with similar skills

Similar skills

CCPM Project Management

Ouroboros PM Interview

Write A Prd

Write Update Tidb Docs

Write Product Spec

Foreman To Issues

More from smallnest/pigo

Architecture Diagram

Related

Questions about To Issues