zoonk-issue-writer

Convert implementation plans into GitHub-ready user stories with acceptance criteria.

146|12|Updated Jan 30, 2025
One-click install
npx skills add https://github.com/zoonk/zoonk --skill zoonk-issue-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zoonk-issue-writer
Source: https://github.com/zoonk/zoonk/tree/main/.agents/skills/zoonk-issue-writer
Command: npx skills add https://github.com/zoonk/zoonk --skill zoonk-issue-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear, actionable user stories from a detailed implementation plan is time-consuming and prone to misinterpretation, slowing down engineering and alignment across teams.

Core Features & Use Cases

  • Generates structured user stories with Context, Goal, Scope, Technical Notes, and Acceptance Criteria from planning inputs.
  • Ensures consistency with existing workflows by producing GitHub-ready issue bodies and links to related issues.
  • Supports post-planning handoff to automation (zoonk-github-issues) for publishing.

Quick Start

Paste the implementation plan into the skill to generate a ready-to-post set of GitHub issues.

Frequently Asked Questions about zoonk-issue-writer

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

FAQPage Schema
How do I convert an implementation plan into GitHub issues with acceptance criteria?

To convert an implementation plan into GitHub issues, paste the plan into the issue writer to generate structured user stories containing Context, Goal, Scope, Technical Notes, and Acceptance Criteria.

What should be included in a user story for GitHub issue tracking?

A complete user story for GitHub issue tracking should include Context, Goal, Scope, Technical Notes, and Acceptance Criteria to ensure engineering alignment and actionable development tasks.

How do I write user stories that capture dependencies and validate scope with stakeholders?

Writing user stories that capture dependencies requires structuring the breakdown from a completed implementation plan, ensuring scope validation with stakeholders before producing the final issue bodies.

Can I automatically publish generated user stories as GitHub issues?

Yes, you can automatically publish generated user stories by handing off the structured output to the zoonk-github-issues tool, which handles the publishing process directly to your repository.

What is the best way to structure user stories for engineering handoff?

The best way to structure user stories for engineering handoff is to break down an implementation plan into discrete stories with Technical Notes and Acceptance Criteria, ensuring GitHub-ready issue bodies.

Do I need a finalized implementation plan before generating user stories?

Yes, you need a finalized implementation plan as input because the user story generation process structures the breakdown, captures dependencies, and validates scope based on those planning inputs.