- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add jabrena/plinth --skill 043-planning-github-issues -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add jabrena/plinth --skill 043-planning-github-issues -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add jabrena/plinth --skill 043-planning-github-issues -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add jabrena/plinth --skill 043-planning-github-issues -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/jabrena/plinth/tree/HEAD/skills/043-planning-github-issuesDo publicador
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.mdVisão geral
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
Perguntas frequentes
Baixe skills/043-planning-github-issues/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/jabrena/plinth.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.