plan-issue

Convert unstructured product ideas into GitHub Issues with implementation plans.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/fsolla/teqo --skill plan-issue-fsolla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-issue
Source: https://github.com/fsolla/teqo/tree/main/.cursor/skills/plan-issue
Command: npx skills add https://github.com/fsolla/teqo --skill plan-issue-fsolla

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill bridges the gap between vague product ideas and structured execution by transforming raw input into detailed, trackable GitHub Issues with comprehensive implementation plans.

Core Features & Use Cases

  • Structured Planning: Generates detailed plans in docs/plans/ including premises, acceptance criteria, and vertical slices.
  • GitHub Integration: Automates the registration of issues with proper labels, priorities, and dependencies.
  • Quality Assurance: Enforces decision-quality gates, ensuring that only well-defined, validated tasks enter the development pipeline.

Quick Start

Use the plan-issue skill to register the idea for a new dashboard analytics feature and create the corresponding implementation plan.

Frequently Asked Questions about plan-issue

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

FAQPage Schema
How do I convert unstructured product ideas into actionable GitHub Issues?

To convert product ideas into GitHub Issues, the skill classifies tasks, performs depth checks on existing code, and defines vertical execution phases to ensure issues meet project standards for priority and dependencies.

What is the best way to create technical implementation plans from raw product ideas?

Creating technical implementation plans involves generating detailed documents in docs/plans/ that include premises, acceptance criteria, and vertical slices to bridge the gap between vague ideas and structured execution.

How does automated issue registration handle priority and dependencies in GitHub?

Automated GitHub issue registration enforces project-specific standards by applying proper labels, defining priorities, and mapping dependencies, ensuring only validated tasks enter the development pipeline through decision-quality gates.

Can I enforce quality assurance checks before adding new tasks to my GitHub roadmap?

Yes, quality assurance is enforced through decision-quality gates that validate task definitions before they enter the development pipeline, ensuring all registered GitHub issues adhere to required project-specific standards.

Do I need existing code in my repository to generate vertical execution phases for new features?

Generating vertical execution phases requires performing depth checks on existing code to accurately classify tasks and define the structured implementation steps needed for the new feature.