skills.rest
seokan-jeong
seokan-jeongCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

team-shinchan:requirements

Decompose feature requests to identify hidden requirements, risks, and dependencies.

8|2|Updated Feb 3, 2026
Search Tags:#feature-analysis#risk-analysis#stakeholder-alignment#requirements-engineering#hidden-requirements#team-shinchan#misae
One-click install
npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-requirements
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-shinchan:requirements
Source: https://github.com/seokan-jeong/team-shinchan/tree/main/skills/requirements
Command: npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hidden requirements and unstated assumptions in feature requests, enabling teams to surface gaps, risks, and ambiguities before implementation.

Core Features & Use Cases

  • Structured requirements interrogation: guides an agent to elicit hidden needs, edge cases, and dependencies.
  • Risk and ambiguity detection: identifies gaps in inputs, conflicting constraints, and potential failure scenarios.
  • Stakeholder alignment: produces clarifying questions and a concise requirements brief for review.

Quick Start

Prompt the agent to perform a hidden requirements analysis on a given feature request and return a structured report.

Frequently Asked Questions about team-shinchan:requirements

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

FAQPage Schema
How do I identify hidden requirements in a feature request?▼

Requirements interrogation works by guiding an agent to decompose vague feature requests into discrete objectives and constraints. It then detects conflicting constraints and potential failure scenarios to produce clarifying questions for stakeholder review.

When do I need to perform a risk and ambiguity analysis on requirements?▼

Yes, requirements interrogation can identify cross-team dependencies by decomposing the feature request objectives and constraints. It produces a structured analysis outlining these dependencies alongside risks and clarifications needed for stakeholder alignment.

What is the best way to uncover unstated assumptions in incomplete requirements?▼

No specific environment setup is required to start hidden requirements analysis. You simply prompt the agent with a given feature request to perform the analysis, and it returns a structured report outlining risks, dependencies, and clarifications.

How do I align stakeholders on vague feature requests before development?▼

The main limitation of hidden requirements analysis is that it relies on the initial feature request quality. If the input lacks any stated objectives or constraints, the resulting clarifying questions and structured analysis may lack the context needed to elicit meaningful stakeholder alignment.

Related Skills

Explore More Product & Management Skills→
thepriceisrightthepriceisright

prd

Generate a structured PRD from a feature brief and save it to tasks/prd-[feature-name].md.

Community
Advanced
dennywu2966dennywu2966

prd

Generate a structured PRD from a feature description with clarifying questions.

Community
Advanced
broomvabroomva
3

pre-mortem

Simulate project failure scenarios to identify and score risks.

Community
Intermediate
viethahongviethahong

prd-writing

Generate PRDs with goals, user flows, requirements, acceptance criteria, and edge cases.

Community
Advanced