Verified:GitHub

scenario-alignment

Generate non-technical business PRD documents aligned with existing codebase and user inputs.

Updated Apr 29, 2026

Search Tags:#PRD generation #product documentation #business alignment #user requirement analysis #feature idea clarification

Ready to run

npx skills add https://github.com/yogogml0035-cpu/Assets --skill scenario-alignment

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scenario-alignment
Source: https://github.com/yogogml0035-cpu/Assets/tree/main/xquant-learning-notes/.agents/skills/scenario-alignment
Command: npx skills add https://github.com/yogogml0035-cpu/Assets --skill scenario-alignment

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill facilitates the alignment of business understanding from user requirements, bugs, plans, or ideas with current code and harness, clarifying decision branches affecting product scope and generating concise, non-technical business PRD documents.

Core Features & Use Cases

Interview-Based Alignment: Iteratively clarify business understanding by aligning with decision trees affecting product scope.
Document Generation: Outputs a refined business PRD document focusing on user goals, scenarios, and product decisions.
Use Case: When a user presents a complex feature idea, this Skill helps to extract the core business intent, align it with existing code and documentation, and produce a clear PRD without technical details.

Quick Start

Activate the scenario-alignment skill and provide the user's feature idea, relevant documents, and harness information.

Frequently Asked Questions about scenario-alignment

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

FAQPage Schema

How do I generate a PRD from a feature idea without including technical details?▼

To generate a non-technical PRD from a feature idea, align business understanding with user scenarios and existing code. This process clarifies decision branches affecting product scope and outputs a concise document focusing on user goals and product decisions.

What is the best way to align business requirements with existing code and harness?▼

The best way to align business requirements with existing code and harness is through interview-based alignment. This method iteratively clarifies business intent from bugs or plans, matching decision trees against current project constraints to produce refined business documentation.

Can I use bug descriptions and business materials as input for product documentation generation?▼

Yes, you can use bug descriptions and business materials as input for product documentation generation. The alignment process handles various user inputs, extracting core business intent and aligning it with current code to produce a clear, non-technical PRD.

Do I need project constraints and codebase access to clarify user requirements and output a PRD?▼

Yes, you need project constraints and codebase access to clarify user requirements effectively. Accessing the codebase allows the alignment process to accurately map user requirements against existing harness capabilities, ensuring the generated PRD reflects actual product scope decisions.

How to clarify complex feature ideas into concise business documents?▼

To clarify complex feature ideas into concise business documents, iteratively align the core business intent with decision trees affecting product scope. This extracts user goals and generates a refined, non-technical business PRD document without technical implementation details.

When should I use an interview-based approach for user requirement analysis?▼

You should use an interview-based approach for user requirement analysis when presented with complex feature ideas or plans. It iteratively clarifies business understanding by identifying decision branches, ensuring the final PRD accurately reflects user scenarios and product scope.