vibeflow-issue-template

mizkun's avatarfrom mizkun

Create or refine VibeFlow issue files under issues/. Use when turning plan items into implementable tasks with clear acceptance criteria.

⭐1stars🔀0forks📁View on GitHub🕐Updated Dec 18, 2025
[Project Management]

When & Why to Use This Skill

The VibeFlow Issue Template skill streamlines the software development lifecycle by automating the creation and refinement of structured issue files. It transforms high-level project plans into granular, implementable tasks, ensuring every ticket includes critical technical details, testable acceptance criteria, and clear architectural requirements to improve development efficiency and code quality.

Use Cases

  • Task Breakdown: Converting high-level roadmap items from a plan.md file into detailed, actionable issue files under the issues/ directory.
  • Requirement Refinement: Enhancing existing task descriptions with unambiguous acceptance criteria and technical specifications to prevent scope creep.
  • Workflow Standardization: Ensuring all team members follow a consistent issue format that includes file locations, dependency tracking, and testing requirements.
  • Technical Documentation: Automatically generating technical implementation approaches and API contracts based on user requests and project state.
namevibeflow-issue-template
descriptionCreate or refine VibeFlow issue files under issues/. Use when turning plan items into implementable tasks with clear acceptance criteria.

VibeFlow Issue Template

When to Use

  • When creating new issue files from plan items
  • When refining existing issues with clearer acceptance criteria
  • When converting user requests into implementable tasks

Output Format (Required)

Every issue file MUST include these sections:

Overview

Brief description of the task (1-2 sentences).

Requirements

  • Bullet list of functional requirements
  • What the implementation must achieve

Acceptance Criteria

  • Testable, unambiguous criteria
  • Each item should be verifiable
  • Include edge cases where relevant

Technical Details

  • Implementation approach
  • Architecture decisions
  • API contracts (if applicable)

File Locations

  • List of files to be created/modified
  • Include paths relative to project root

Testing Requirements

  • Unit test requirements
  • Integration test requirements (if applicable)
  • E2E test requirements (if applicable)

Dependencies

  • Other issues this depends on
  • External dependencies (packages, APIs)

Non-goals (optional)

  • What is explicitly out of scope

Instructions

  1. Read context first: Always read spec.md and plan.md before creating issues.
  2. Check state: Read .vibe/state.yaml to understand current phase.
  3. Create file: Write to issues/<issue-name>.md.
  4. Verify completeness: Ensure all required sections are present.
  5. Cross-reference: Link to related issues if applicable.

Examples

  • "Create an issue for user authentication"
  • "Turn plan item 2.1 into an implementable issue"
  • "Refine issue-001 with clearer acceptance criteria"