researcher

Convert raw user input into an RFC 2119-prioritized SRS with acceptance criteria.

9|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/TykoDev/SupremeTeam --skill researcher-tykodev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: researcher
Source: https://github.com/TykoDev/SupremeTeam/tree/main/skills/design/researcher
Command: npx skills add https://github.com/TykoDev/SupremeTeam --skill researcher-tykodev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill reduces ambiguity and risk by converting informal project prompts, stakeholder input, and high-level visions into a comprehensive, testable Software Requirements Specification and domain analysis that downstream designers and engineers can act on.

Core Features & Use Cases

  • Structured SRS: Produces an ISO/IEC/IEEE 29148-aligned SRS with document metadata, scope, stakeholder registry, functional requirements using RFC 2119 priorities and GIVEN/WHEN/THEN acceptance criteria, and mapped non-functional requirements.
  • Domain Analysis & DDD: Applies event storming, bounded context mapping, core domain identification, entity templates, and a ubiquitous language glossary to produce actionable domain models.
  • Review-Ready Deliverables: Packages deliverables with a gatekeeper-ready review packet, supports pipeline and standalone review loops, and follows a persistent save protocol when requested.
  • Use Case: Product managers, commanders, and business analysts use this skill to convert stakeholder interviews or ticket-level requests into a validated SRS and domain model before architecture and implementation.

Quick Start

Use the researcher skill to gather requirements and produce an SRS and domain analysis for a new project.

Frequently Asked Questions about researcher

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

FAQPage Schema
How do I convert stakeholder interviews into a structured SRS with acceptance criteria?

To convert stakeholder interviews into a structured SRS, you gather raw input and extract project vision, stakeholders, and constraints. The process yields an ISO/IEC/IEEE 29148-aligned SRS featuring RFC 2119-prioritized functional requirements with GIVEN/WHEN/THEN acceptance criteria.

What is the best way to generate a domain analysis using event storming and bounded contexts?

Generating a domain analysis using event storming involves processing raw project prompts to identify core domains and map bounded contexts. This yields actionable domain models complete with entity templates and a ubiquitous language glossary.

How do I map non-functional requirements to ISO 25010 thresholds?

You map non-functional requirements to ISO 25010 thresholds by extracting NFRs from raw user input during project inception. The system processes these constraints to produce an SRS with mapped non-functional requirement thresholds.

Can I use domain-driven design to extract a ubiquitous language glossary from raw project prompts?

Yes, you can use domain-driven design to extract a ubiquitous language glossary from raw project prompts. The skill applies DDD principles to process informal visions and produce a structured domain model containing the glossary.

Does requirements engineering work with commander-delegated pipeline phases?

Yes, requirements engineering works with commander-delegated pipeline phases. The skill can apply its requirements gathering logic during these delegated phases or direct user requests to extract project vision and produce a validated SRS.

When do I need an ISO 29148-aligned SRS review packet?

You need an ISO 29148-aligned SRS review packet when preparing for project inception or gatekeeper reviews. The skill packages deliverables into a review-ready format, supporting both standalone review loops and persistent save protocols.