decomposing-intent

Decompose feature requests into structured tasks and research questions.

8|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/bostonaholic/team --skill decomposing-intent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decomposing-intent
Source: https://github.com/bostonaholic/team/tree/main/skills/decomposing-intent
Command: npx skills add https://github.com/bostonaholic/team --skill decomposing-intent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the ambiguity of high-level feature requests by enforcing a rigorous decomposition process that separates user intent from technical research requirements.

Core Features & Use Cases

  • Artifact Generation: Automatically creates standardized task, question, and repository scope documents to guide agent workflows.
  • Multi-Repo Detection: Intelligently identifies and validates cross-repository dependencies to ensure the pipeline operates across the correct codebase boundaries.
  • Use Case: When a user requests a cross-cutting feature like adding rate limiting across multiple services, this skill structures the intent and generates the necessary research questions to ensure the implementation is technically sound and scoped correctly.

Quick Start

Invoke the decomposing-intent skill to process a new feature request by providing the task description to the orchestrator.

Frequently Asked Questions about decomposing-intent

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

FAQPage Schema
How do I break down vague feature requests into structured task definitions for agentic workflows?

Decomposing intent breaks down vague feature requests by separating user intent from technical research requirements, generating standardized task definitions and neutral research questions to guide multi-phase agentic workflows.

What is the best way to plan tasks for cross-cutting features across multiple repositories?

Task planning for multi-repo features involves intelligently identifying and validating cross-repository dependencies to ensure the pipeline operates across correct codebase boundaries, generating standardized markdown artifacts for execution.

How does requirement engineering work for generating standardized markdown artifacts in agent workflows?

Requirement engineering for agent workflows operates by validating repository scope and generating standardized markdown artifacts with strict frontmatter schemas, enforcing codebase-focused inquiry patterns to ensure technical alignment.

Can I use this decomposition approach to validate repository scope before generating research questions?

Yes, repository scope validation is a core mechanism that operates before generating neutral research questions, ensuring technical alignment by enforcing strict frontmatter schemas and codebase-focused inquiry patterns across the pipeline.

Do I need specific dependencies to structure high-level user intent into execution plans?

No specific dependencies are required to structure high-level user intent into execution plans; the process relies solely on providing the task description to the orchestrator to generate the necessary standardized artifacts.

Why does task decomposition separate user intent from technical research requirements?

Task decomposition separates user intent from technical research requirements to solve the ambiguity of high-level feature requests, ensuring implementation is technically sound and scoped correctly by generating neutral research questions.