ralph-func-analyst

Conducts interactive requirement pre-analysis and generates a pre-requirements.md document.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Wishtohear/bucket-water-oms --skill ralph-func-analyst-wishtohear
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ralph-func-analyst
Source: https://github.com/Wishtohear/bucket-water-oms/tree/main/.trae/skills/ralph-func-analyst
Command: npx skills add https://github.com/Wishtohear/bucket-water-oms --skill ralph-func-analyst-wishtohear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns a vague product idea into a structured requirement reference document through guided human-AI dialogue, preventing teams from jumping into planning before the scope is mutually confirmed. ## Core Features & Use Cases - Probing Protocol: Asks targeted questions about core features, target users, pain points, and tech preferences to uncover hidden requirements. - Requirement Structuring: Organizes confirmed dialogue into a pre-requirements.md file containing project name, elevator pitch, key features, user stories, and constraints. - Scope Guardrails: Explicitly excludes field-level details, edge cases, technical implementation, and non-user functionality to keep the analysis at the right altitude. - Use Case: A user says "I want to build a Twitter-like social app." The Skill asks clarifying questions, confirms the feature breadth with the user, then writes a pre-requirements.md ready for downstream Ralph planning. ## Quick Start Ask the assistant to perform a requirement pre-analysis of your product idea and organize it into a requirement document.

Frequently Asked Questions about ralph-func-analyst

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

FAQPage Schema
How do I run a requirement pre-analysis before project planning?▼

Explicitly request a requirement pre-analysis or ask to organize a requirement document. The Skill then asks probing questions about features, users, and pain points, and writes the confirmed results into a pre-requirements.md file.

What does the pre-requirements.md output document contain?▼

The document contains the project name, a one-sentence elevator pitch, a key features list, user stories, and technical or time constraints. It serves as a reference for downstream planning, not a binding contract.

When is this requirement analysis skill triggered?▼

It runs strictly on demand, only when the user explicitly asks for requirement pre-analysis, idea analysis, or requirement document organization. Without an explicit instruction, it does not activate on its own.

What topics are excluded from the requirement pre-analysis?▼

It excludes field-level details, button and input specifications, error and boundary handling, technical implementation such as databases and APIs, and non-user functionality like background jobs or ops tooling.

Can the requirement document be generated without any user dialogue?▼

No, the Skill requires interactive questioning before producing the final document. Direct generation is only acceptable when the user's initial instruction is already extremely detailed.