Skill: Create Issue
Skill: Create Issue
Issue Creator agent workflow. Reads a plan phase, explores the codebase, and proposes a well-formed Forgejo issue for user review.
Steps
- Read the plan —
mcp__pal-e-docs__get_note(slug="<plan-slug>"). Identify the target phase. Understand the full plan context — vision, decisions made, and how this phase fits. - Read the project page —
mcp__pal-e-docs__get_note(slug="project-<project-slug>"). Understand current status, architecture, repos, and open issues. - Read the issue template —
mcp__pal-e-docs__get_note(slug="template-issue"). This defines the required sections. Follow it exactly. - Check for duplicates —
mcp__forgejo__list_issues(owner="forgejo_admin", repo="<repo>"). Don't propose an issue that already exists. - Explore the codebase — Use Read, Glob, Grep to understand what files and code the phase will touch. This makes the issue's Acceptance Criteria concrete and specific.
- Draft the issue — Write title + body following
template-issue: - Present and stop — Show the proposed title and body to the user. Do not create the issue. Wait for approval.
MCP Tools
| Step | Tool | Purpose |
|---|---|---|
| 1 | <code>mcp__pal-e-docs__get_note</code> | Read plan note |
| 2 | <code>mcp__pal-e-docs__get_note</code> | Read project page |
| 3 | <code>mcp__pal-e-docs__get_note</code> | Read issue template |
| 3 | <code>mcp__pal-e-docs__list_notes</code> | Discover relevant SOPs/conventions |
| 4 | <code>mcp__forgejo__list_issues</code> | Check for duplicate issues |
| 4 | <code>mcp__forgejo__get_repo</code> | Confirm target repo |
Agent
agent-issue-creatorRelated
skill-implement-phase— Dev Agent picks up after issue is approvedtemplate-issue— the template this skill followsagent-issue-creator— the agent that runs this skill