work-research

Investigate topics, bugs, test cases, legacy code, and migrations into structured research reports.

Updated May 8, 2026
One-click install
npx skills add https://github.com/juanca202/sdd-devkit --skill work-research-juanca202
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-research
Source: https://github.com/juanca202/sdd-devkit/tree/main/skills/work-research
Command: npx skills add https://github.com/juanca202/sdd-devkit --skill work-research-juanca202

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Before specifying, planning, or implementing work, teams need answers: Is this viable? Why does this bug happen? Does this test case really verify its requirement? What does this legacy code actually do? This Skill turns those open questions into standardized, evidence-backed research reports (RS-XXX) instead of scattered chat answers. ## Core Features & Use Cases - Six routed investigation flows: free-topic research, pending-decision analysis for US/TK/WI artifacts, bug/issue diagnosis with root cause and test-gap analysis, test case auditing, legacy code reverse-engineering into features (FT-XXX), and cross-project migration discovery. - Standardized output: every investigation produces a research/RS-XXX-{slug}/ folder with a README.md report built from templates, plus flow-specific files like discovery.md, analysis.md, or a bug dossier. - Project manager integration: reads work items from Azure DevOps via MCP and routes them to the right flow by type, in read-only mode. - Use Case: A user reports "falla en producción el cálculo de tarifas". The Skill routes to the issue flow, reproduces the defect, identifies the root cause with file and symbol evidence, diagnoses why existing tests missed it, and hands off a bug-fix work item to the planning skill. ## Quick Start Ask the agent to investigate a topic, analyze a bug, audit a test case, or reverse-engineer legacy code, for example: "Investiga por qué falla el login en producción y genera el informe."

Frequently Asked Questions about work-research

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

FAQPage Schema
How do I investigate a bug before fixing it?▼

Describe the defective behavior or pass a bug identifier, and the issue flow reproduces it, finds the root cause with file and symbol evidence, and diagnoses why existing tests missed it. The output is a bug dossier handed off to the planning skill as a bug-fix work item.

How to reverse-engineer requirements from legacy code?▼

The legacy flow inventories technical artifacts, reconstructs use cases, groups them into capabilities and cohesive features, and extracts business rules, each citing code evidence. It then creates FT-XXX feature documents and hands off test case definition to test-define.

Does work-research integrate with Azure DevOps?▼

Yes, it reads work items from Azure DevOps via MCP and routes them by type: user stories and tasks go to decision analysis, bugs to issue analysis, and test cases to test auditing. The integration is read-only; it never creates or modifies work items.

When does the skill write research reports to disk?▼

Nothing is written until the user confirms the complete report content presented in chat. After confirmation, it creates the research/RS-XXX-{slug}/ folder with the README.md report and any flow-specific additional files.

What is the difference between the legacy and migration flows?▼

Legacy analysis documents existing code as features and test cases in place, while migration analysis maps technology between a source and target project, assesses golden master testing opportunities, and sizes the change for handoff to definition or planning skills.