analyst

Transform research reports into structured requirements documents and user stories.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/Denissvgn/project-team-ag --skill analyst-denissvgn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyst
Source: https://github.com/Denissvgn/project-team-ag/tree/main/.agent/skills/analyst
Command: npx skills add https://github.com/Denissvgn/project-team-ag --skill analyst-denissvgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms raw research into clear, actionable requirements.

Core Features & Use Cases

  • Requirements Engineering: Define functional and non-functional requirements with traceable dependencies.
  • User Story Creation: Write precise user stories with acceptance criteria and testable outcomes.
  • Specification Writing: Create detailed technical specifications and mapping to stakeholders.
  • Dependency Mapping: Identify and document relationships between requirements and tasks.

Quick Start

Provide the Research Report and Vision/Scope to the Analyst; generate a structured Requirements Document and accompanying User Stories with acceptance criteria ready for handoff.

Frequently Asked Questions about analyst

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

FAQPage Schema
How do I turn raw research into actionable requirements?

To turn raw research into actionable requirements, provide the research report and vision scope to generate a structured Requirements Document with traceable dependencies for product development.

How do I write user stories with acceptance criteria from research data?

Writing user stories with acceptance criteria from research data involves transforming raw findings into precise stories with testable outcomes and mapping dependencies for cross-functional handoffs.

What is dependency mapping in requirements engineering?

Dependency mapping in requirements engineering is the process of identifying and documenting relationships between functional requirements, tasks, and stakeholders to ensure traceable cross-functional handoffs.

How do I create a Requirements Document for technical specifications?

Creating a Requirements Document for technical specifications requires defining functional and non-functional requirements, writing user stories, and mapping dependencies across planning and verification phases.

Can I use this for requirements engineering without existing dependencies?

Yes, you can use this for requirements engineering without existing dependencies because the Skill operates independently to define functional requirements and document new dependency relationships from scratch.