fabrico-research

name	fabrico-research
description	Research a task and produce a comprehensive research document.

Invocation portability: $fabrico-* below means the discovered entry workflow. Use the unqualified name for repository or filesystem installs and $fabrico-collections:fabrico-* for plugin installs.

Input

Use the user’s current request as the workflow input. Expected context: [Jira ID or task description].

Research the task based on the provided Jira ID or task description. The file outcome should be a markdown file named after the task Jira ID in kebab-case format or after task name (if no Jira task provided) with .research.md suffix (e.g., user-authentication.research.md). The file should be placed in the specifications directory under a folder named after the issue ID or the shortened task name in kebab-case format.

It should contain every relevant information needed to build a comprehensive context for the task or feature.

Required Skills

Before starting, load and follow these skills:

• fabrico-task-analysing - for the structured research process and output template
• fabrico-codebase-analysing - for analyzing the existing codebase in the context of task requirements

Workflow

1. Gather all information related to the task from the codebase, Atlassian tools (Jira, Confluence) and other relevant sources.
2. Analyze the task thoroughly, including its parents and subtasks if applicable, to get the full picture of the requirements.
3. Analyse the tech stack, industry and domain of the project to understand best practices that should be applied during implementation.
4. Check all external links added to the task. Make sure to check the confluence pages linked to the task to gather more information about requirements and processes. If any PDF documents are attached, referenced, or linked, use the pdf-reader tool to extract and review their content.
5. Unless asked to research only non-frontend aspects, in case there are Figma designs linked to the task, review all of them using the figma MCP server (it's very important) and include relevant information in the context.
6. Analyze if there are any ambiguities or missing information in the task description. If there are any ask for clarification before finalizing the context.
7. Don't provide implementation details, focus on gathering requirements, user stories, acceptance criteria and key flows.
8. Save the gathered information following the research.example.md template from the fabrico-task-analysing skill.
9. Ensure that the research file is clear, concise, and tailored to the needs of the development team.

Follow the template structure and naming conventions strictly to ensure clarity and consistency.

In case of any ambiguities or missing information in the task description, ask for clarification before finalizing the context.

Update the research file after each interaction if new information is gathered.