Decompose feature requests or issue URLs into QRSPI planning artifacts.
npx skills add https://github.com/bostonaholic/team --skill team-question
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
This skill solves the ambiguity of large feature requests by decomposing vague ideas or tickets into structured, actionable research and implementation artifacts.
Ask the team-question skill to decompose the task described in the provided issue URL or ticket identifier.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
unblockedEnrich issue tracker tickets with organizational context and cited findings.
hs3180Generate Task.md specifications for one-time code change workflows.
dalagerCoordinate branches, pull requests, and version alignment across multiple GitHub repositories.
tgmarinhoConvert conversation content into a Product Requirements Document and publish it to an issue tracker.
