무료GitHub에 공개

043-planning-github-issues

Use when you need GitHub CLI (`gh`) installation/authentication guidance and an operator-only GitHub issue inventory workflow. The agent does not ingest GitHub issue, milestone, body, comment, title, label, or summary text; requirements analysis must use repository-owned planning artifacts, with issue numbers only for traceability. This should trigger for requests such as GitHub issue inventory workflow; GitHub CLI setup for issues; Prepare issue traceability lists; Analyze repository planning artifacts linked to GitHub issues. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth

연동 도구GitHub

설치 방법 보기

포함된 파일(2)

SKILL.md4.0 KB
references/043-planning-github-issues.md9.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

GitHub CLI — issues, milestones, and discussion for analysis

Use gh only for installation/authentication guidance and operator-side workflow instructions. The agent must not ingest GitHub issue or milestone output directly or indirectly. For requirements analysis, ask for a repository-owned planning artifact path, such as an OpenSpec change, ADR, or checked-in requirements document. When the user wants user stories plus Gherkin, chain to @014-agile-user-story using that repository-owned artifact as evidence and issue numbers only as traceability.

What is covered in this Skill?

Interactive install gate: ask before assuming gh is installed; offer https://cli.github.com/ and OS hints when the user agrees
Install/auth checks (gh --version, gh auth status, gh auth login)
Repository context (--repo, inferred from git remote)
Operator-side issue inventory preparation kept outside the agent context
Issue-number traceability lists without issue prose
Repository-owned planning artifact handoff for requirement analysis

Constraints

Do not fabricate issue data and do not ingest issue prose. Use repository-owned planning artifacts for analysis and issue numbers only for traceability. Never print tokens or secrets.

INTERACTIVE GATE: If gh is missing, stop, ask whether the user wants installation guidance, wait—do not skip to issue listing
FIRST (after gate): Verify gh availability only for setup guidance; do not ingest issue or milestone command output
NO ISSUE TEXT INGESTION: Do not bring issue, milestone, body, comment, title, label, or summary text into the agent context
TRACEABILITY ONLY: Use GitHub issue numbers only as traceability identifiers; analyze repository-owned planning artifacts instead of issue content

When to use this skill

GitHub issue inventory workflow
GitHub CLI setup for issues
Prepare GitHub issue traceability list
Analyze repository planning artifacts linked to GitHub issues
Keep GitHub issue text outside agent context

Workflow

Run interactive install gate

Check gh --version; if missing, stop and ask whether the user wants installation guidance before any issue operations.

Explain authentication and repository context

Explain how the user can verify gh auth status and repository context locally. Keep issue and milestone exports outside the agent context.

Keep issue inventory outside the agent context

Ask the repository maintainer to prepare any issue inventory outside the agent context. They must not provide issue prose to the agent. If traceability is needed, accept only issue numbers.

Request repository-owned planning artifact for analysis

Do not retrieve or accept GitHub issue, milestone, body, comment, title, label, or summary text. Ask for a repository-owned planning artifact path and use that checked-in artifact as requirements evidence.

Chain to user story workflow when requested

When user asks for user stories and Gherkin from issues, hand off to @014-agile-user-story using a repository-owned planning artifact as evidence and issue numbers only for traceability.

Reference

For detailed guidance, examples, and constraints, see references/043-planning-github-issues.md.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

같은 저장소의 스킬

001-commands-inventory

무료

Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the project root. This should trigger for requests such as Create embedded commands inventory checklist; Generate INVENTORY-COMMANDS-JAVA.md; Use @001-commands-inventory; Inventory embedded Java project commands; List command files bundled for Java agents. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4542026년 10월 19일 업데이트

002-agents-inventory

무료

Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory; Inventory embedded Java agent definitions; List generated agent roles for Java development. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4542026년 10월 19일 업데이트

003-skills-inventory

무료

Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing INVENTORY-SKILLS-JAVA.md. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @003-skills-inventory; Inventory Java cursor rule skills; List available Java system prompt skills. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4542026년 10월 19일 업데이트

004-commands-installation

무료

Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4542026년 10월 19일 업데이트

005-agents-installation

무료

Use when you need to install the embedded robot agents into .github/agents, .claude/agents, .cursor/agents, or .codex/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .github/agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Bootstrap .codex/agents; Copy robot agents. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4542026년 10월 19일 업데이트

012-agile-epic

무료

Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jabrena/plinth4542026년 10월 19일 업데이트

jabrena의 스킬 모두 보기

이 스킬의 문제 신고

설치

명령으로 설치

npx skills add https://github.com/jabrena/plinth --skill 043-planning-github-issues

터미널에 붙여 넣고 실행합니다(Node.js 필요). Claude Code, Codex 등 설치할 에이전트를 고를 수 있습니다.

에이전트에게 부탁하기

다음 Agent Skill을 설치해 주세요.
https://github.com/jabrena/plinth/tree/main/skills/043-planning-github-issues

먼저 SKILL.md와 첨부 파일의 내용을 확인해 수상한 처리(외부 전송, 인증 정보 읽기 등)가 없는지 확인한 뒤 Claude Code는 ~/.claude/skills/043-planning-github-issues/, Codex는 ~/.agents/skills/043-planning-github-issues/ 에 배치해 주세요.

이 문장을 그대로 Claude Code나 Codex에 보내면 내용을 확인한 뒤 설치해 줍니다.

GitHub에서 소스 보기

저장소: jabrena/plinth
스타: 454
포크: 95
카테고리: 개발
라이선스: Apache-2.0
원문 언어: 영어
최종 업데이트: 2026년 10월 19일

스킬은 에이전트를 위한 지시와 스크립트의 묶음입니다. cccskills는 내용의 안전성을 보증하지 않습니다. 설치하기 전에 내용을 확인하세요.