analyst

Interview stakeholders to classify software change risk and generate discovery.md.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/javierhbr/agnostic-agent-loop --skill analyst-javierhbr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyst
Source: https://github.com/javierhbr/agnostic-agent-loop/tree/main/internal/skills/packs/sdd/analyst
Command: npx skills add https://github.com/javierhbr/agnostic-agent-loop --skill analyst-javierhbr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the critical need for thorough risk assessment before engineering work begins, ensuring that high-impact changes are identified and managed proactively.

Core Features & Use Cases

  • Risk Assessment: Conducts interviews to gather evidence for classifying changes.
  • Discovery Document Generation: Produces a discovery.md detailing problem, evidence, affected components, risk, and decisions.
  • Use Case: Before deploying a change that could affect core user authentication, the Analyst agent interviews stakeholders, gathers performance metrics, identifies all impacted services, and classifies the risk as 'Critical', ensuring proper review and planning.

Quick Start

Use the analyst skill to assess the risk for the initiative 'User Authentication'.

Frequently Asked Questions about analyst

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

FAQPage Schema
How do I conduct a risk assessment interview for software changes?

Risk assessment interviews gather evidence from stakeholders to classify change risk. The Skill asks targeted questions, identifies affected components, and generates a discovery.md documenting problem statements, evidence, and key decisions needed.

What is a discovery document in software change management?

A discovery document details problem statements, evidence, affected components, risk classification, and key decisions needed. It ensures thorough risk assessment before engineering work begins and operates within the SDD v3.0 Full workflow for high or critical changes.

When do I need to perform risk classification for a software deployment?

Risk classification is needed before deploying changes that could affect core systems. The Skill interviews stakeholders, gathers performance metrics, identifies impacted services, and classifies risk to ensure proper review and proactive management.

How do I classify change risk based on evidence instead of guesswork?

Classifying change risk with evidence involves conducting interviews to gather performance metrics and stakeholder input. The Skill uses this evidence to categorize risk levels and document affected components within a discovery.md file.

Can I use this risk assessment process within an SDD v3.0 workflow?

The risk assessment process operates within the SDD v3.0 Full workflow specifically for high and critical risk changes. It produces a discovery document that feeds into downstream compliance and change management steps.

What should be included in a discovery document for critical software changes?

A discovery document should include problem statements, gathered evidence, affected components, risk classification, and key decisions needed. This ensures all impacted services are identified for proper review and planning before engineering work begins.