implement-issue

Implement GitHub issue workflows from user story analysis to pull request creation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/zorgentech/archon --skill implement-issue-zorgentech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-issue
Source: https://github.com/zorgentech/archon/tree/main/.claude/skills/implement-issue
Command: npx skills add https://github.com/zorgentech/archon --skill implement-issue-zorgentech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, guarded workflow to take a GitHub issue from initial analysis to a merged pull request, ensuring code quality, documentation updates, and project board state transitions without ad-hoc steps or missed checks.

Core Features & Use Cases

  • Analyze and validate a user story for scope, acceptance criteria, and dependencies before implementation.
  • Create an isolated worktree and feature branch, implement changes with segmented conventional commits, run build and test checks, update documentation, and create a linked PR.
  • Automate project board status updates, post-PR validations, and hand off to the merge-resolution skill to finish the lifecycle.
  • Use Case: A developer assigned an ARCHON issue can run this workflow to produce a CI-green PR that closes the issue and updates relevant docs.

Quick Start

Run the implement-issue skill with the GitHub issue number to start planning, implement changes in an isolated worktree, validate tests and linting, update docs, and open a PR.

Frequently Asked Questions about implement-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue implementation from start to a merged pull request?

Automating GitHub issue implementation involves analyzing the user story, planning changes, creating a feature branch, committing code, running tests, and opening a pull request. This workflow ensures CI validation and project board updates occur end-to-end.

What is the end-to-end workflow for turning a GitHub issue into a pull request?

The end-to-end workflow for turning a GitHub issue into a pull request covers issue triage, isolated worktree creation, segmented conventional commits, documentation updates, and CI checks. It links the final pull request back to the original issue for automated closure.

Do I need GitHub CLI authentication to automate branch creation and pull requests?

Yes, GitHub CLI authentication is required to automate branch creation and pull requests. You also need git workspace control and explicit permissions to push branches, create pull requests, and edit project board items within the target repository.

How to update project board status automatically when opening a pull request?

Updating project board status automatically when opening a pull request requires linking the branch to the issue and triggering state transitions. The workflow automates these post-PR validations and board updates as part of the issue implementation lifecycle.

Can I use git worktrees to isolate feature branch changes for GitHub issues?

Yes, you can use git worktrees to isolate feature branch changes for GitHub issues. The workflow creates an isolated worktree to implement changes, ensuring local test and build checks run cleanly before pushing the branch and opening a pull request.

What are the limitations of automating issue triage and pull request workflows?

Limitations of automating issue triage and pull request workflows include strict dependencies on CONTRIBUTING.md adherence and local test checks. The workflow requires explicit repository permissions and cannot bypass CI validation or merge steps without a follow-up review process.