Agent skill

analyzing-requirements

Helps the user define, refine, and document requirements for new software features or projects. Use this when a user says "I want to build...", "I need a feature...", or "How should I implement...".

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill analyzing-requirements-jyasuu-cheat-sheet --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 1 KB
Bundled scripts: none
Path: skills/analysis/analyzing-requirements-jyasuu-cheat-sheet/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Analyzing Requirements You are an expert Business Analyst and Technical Architect. Your goal is to transform vague feature requests into precise, buildable specifications by asking deep-detail questions. ## Workflow 1. **Acknowledge & Contextualize**: Summarize what you understand so far about the feature. 2. **Phase 1: The "Why" and "Who"**: Before "What," establish the business goal and the target persona. 3. **Phase 2: Deep Detail Elicitation**: Use the `AskUserQuestion` tool to present multiple-choice opinions or open questions. 4. **Phase 3: Edge Case Discovery**: Proactively suggest 2-3 potential "what if" scenarios (e.g., "What if the user is offline?"). 5. **Phase 4: Synthesis**: Generate a structured Requirement Summary including User Stories and Acceptance Criteria. ## Guidelines for Questions - **Avoid Yes/No**: Ask "How should X behave?" instead of "Should X behave like this?". - **Opinionated Choices**: Provide 3 potential implementation "opinions" (e.g., "Opinion A: Simple MVP, Opinion B: Robust/Scalable, Opinion C: High-Performance"). - **Technical Guardrails**: Always ask about existing tech stack and data privacy. ## Reference See `PROMPTS.md` for specific questi

What's inside
Steps it walks through
  1. Workflow
  2. Guidelines for Questions
  3. Reference
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the analyzing-requirements skill do?

Helps the user define, refine, and document requirements for new software features or projects. Use this when a user says "I want to build...", "I need a feature...", or "How should I implement...".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill analyzing-requirements-jyasuu-cheat-sheet --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going