team-question

Decompose feature requests or issue URLs into QRSPI planning artifacts.

8|1|Updated Mar 28, 2026

Search Tags:#workflow #planning #orchestration #decomposition #agentic #task-management

Ready to run

npx skills add https://github.com/bostonaholic/team --skill team-question

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-question
Source: https://github.com/bostonaholic/team/tree/main/skills/team-question
Command: npx skills add https://github.com/bostonaholic/team --skill team-question

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the ambiguity of large feature requests by decomposing vague ideas or tickets into structured, actionable research and implementation artifacts.

Core Features & Use Cases

Intent Decomposition: Automatically generates task.md and questions.md to clarify human intent and identify necessary research.
Contextual Discovery: Grounds requests in repository history and README context when specific details are missing.
Multi-Repo Support: Detects cross-repository dependencies and initializes multi-repo workflows automatically.
Use Case: When a developer is assigned a vague ticket like "Add rate limiting," this skill creates the necessary plan files and research questions to ensure the implementation phase is well-defined.

Quick Start

Ask the team-question skill to decompose the task described in the provided issue URL or ticket identifier.

Frequently Asked Questions about team-question

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

FAQPage Schema

How do I decompose a vague feature request into an actionable development plan?▼

Task decomposition breaks down vague feature requests by analyzing repository context to generate structured planning artifacts like task.md and questions.md. This clarifies human intent and identifies necessary research before implementation begins.

What is the best way to generate research questions for a complex software ticket?▼

Generating research questions for complex tickets involves analyzing repository history and README context to produce a questions.md file. This grounds the ambiguous ticket details in actual project constraints and expectations.

Can I use an issue URL to automatically create a task planning workflow?▼

Yes, you can use an issue URL to automatically create a task planning workflow. The skill fetches issue details via CLI tools and decomposes them into QRSPI planning artifacts within the docs/plans/ directory.

Does this task planning approach support multi-repo dependencies?▼

Yes, this task planning approach supports multi-repo dependencies. It detects cross-repository dependencies automatically and initializes multi-repo workflows to ensure distributed planning artifacts are properly mapped.

Do I need a local file system to manage generated planning documents?▼

Yes, you need a local file system to manage generated planning documents. The decomposition process requires integration with local directories to store and manage the task.md, questions.md, and optional PRD files.

When should I avoid using automated task decomposition for feature planning?▼

You should avoid using automated task decomposition when specific repository details are missing and context cannot be reliably inferred from the README or history, which may result in inaccurate or ungrounded planning artifacts.