analyze

Analyzes project requirements and current code context to validate completeness.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Kaze-sn/Vibe-code --skill analyze-kaze-sn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/Kaze-sn/Vibe-code/tree/main/skills/helloagents/analyze
Command: npx skills add https://github.com/Kaze-sn/Vibe-code --skill analyze-kaze-sn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps validate requirements completeness and analyze the current code context to inform solution design during the requirements analysis phase.

Core Features & Use Cases

  • Requirement scoring to assess clarity, completeness, and readiness for design
  • Guided follow-up prompts to elicit missing details without duplicating known information
  • Step-by-step code analysis preparation to identify modules, risks, and constraints

Quick Start

Run the analyze skill on your project to trigger the requirements assessment workflow.

Frequently Asked Questions about analyze

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

FAQPage Schema
How do I score project requirements for clarity and completeness before design?

Requirements scoring assesses project requirements for clarity, completeness, and readiness to validate completeness before design. It applies a structured analysis workflow to evaluate readiness and inform subsequent design decisions.

What is the best way to analyze current code context for risk assessment?

Analyzing current code context for risk assessment involves a step-by-step code analysis workflow that identifies modules, risks, and constraints. This validates the current code context to inform solution design and mitigate potential issues.

How do I elicit missing project requirements without duplicating known information?

To elicit missing project requirements without duplicating known information, use guided follow-up prompts. These prompts target specific gaps in the requirements to validate completeness and elicit missing details efficiently.

Can I use structured requirements analysis for major changes to an existing codebase?

Yes, structured requirements analysis applies to both new projects and major changes to an existing codebase. It triggers a formal requirements review and subsequent code analysis to validate completeness and inform design decisions.

When do I need a formal requirements review and code analysis workflow?

A formal requirements review and code analysis workflow is needed for new projects and major changes. This structured process validates requirements completeness, scores readiness, and identifies code constraints to inform solution design.