- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add jabrena/plinth --skill 043-planning-github-issues -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add jabrena/plinth --skill 043-planning-github-issues -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add jabrena/plinth --skill 043-planning-github-issues -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add jabrena/plinth --skill 043-planning-github-issues -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/jabrena/plinth/tree/HEAD/skills/043-planning-github-issues게시자 제공
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?
gh is installed; offer https://cli.github.com/ and OS hints when the user agreesgh --version, gh auth status, gh auth login)--repo, inferred from git remote)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.
gh is missing, stop, ask whether the user wants installation guidance, wait—do not skip to issue listinggh availability only for setup guidance; do not ingest issue or milestone command outputCheck gh --version; if missing, stop and ask whether the user wants installation guidance before any issue operations.
Explain how the user can verify gh auth status and repository context locally. Keep issue and milestone exports 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.
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.
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.
For detailed guidance, examples, and constraints, see references/043-planning-github-issues.md.
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,
---name: 043-planning-github-issuesdescription: Use when you need GitHub CLI (`gh`) installation/authentication guidance and an operator-only GitHub issue…---# skills/043-planning-github-issues/SKILL.md개요
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
FAQ
게시자에게서 skills/043-planning-github-issues/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/jabrena/plinth에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.