evaluate

Guide software design by clarifying requirements and obtaining approval before implementation.

Updated Feb 22, 2026

Search Tags:#workflow #design #planning #ideation #requirements #validation

Ready to run

npx skills add https://github.com/jpeggdev/buildwithjpegg --skill evaluate-jpeggdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: evaluate
Source: https://github.com/jpeggdev/buildwithjpegg/tree/main/plugins/development-workflow/skills/evaluate
Command: npx skills add https://github.com/jpeggdev/buildwithjpegg --skill evaluate-jpeggdev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that all creative work, from new features to minor modifications, begins with a thorough understanding of user intent, requirements, and a validated design, preventing wasted implementation effort.

Core Features & Use Cases

Requirement Clarification: Asks targeted questions to refine ideas and understand constraints.
Design Exploration: Proposes multiple approaches with trade-offs before settling on a solution.
Incremental Validation: Presents design sections for user approval before proceeding.
Use Case: Before adding a new user authentication flow, this skill will guide you through defining the exact requirements, exploring security implications, and presenting a clear architectural design for your approval.

Quick Start

Use the evaluate skill to begin designing the new user authentication flow.

Frequently Asked Questions about evaluate

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

FAQPage Schema

How do I design software features before starting implementation?▼

To design software features before implementation, use a structured design-first workflow that clarifies user intent, proposes alternative approaches, and validates requirements incrementally to prevent scope creep. This ensures all creative work begins with a validated specification.

Why does premature coding cause scope creep in software development?▼

Premature coding causes scope creep because it skips requirement clarification and design validation. Without a strict design-first methodology to explore constraints and obtain explicit approval, implementation effort is wasted on unvalidated assumptions.

What is the best way to clarify requirements for a new authentication flow?▼

The best way to clarify requirements for a new authentication flow is through targeted questions that explore user intent, define exact constraints, and assess security implications before proposing architectural designs for incremental validation.

How do I explore design alternatives and trade-offs for software modifications?▼

To explore design alternatives and trade-offs for software modifications, apply a design-first process that proposes multiple approaches, evaluates their respective constraints, and presents them for explicit user approval before any coding begins.

Can I use a design-first methodology for minor software modifications?▼

Yes, you can use a design-first methodology for minor modifications. It ensures all creative work, regardless of scale, begins with thorough understanding of user intent, requirements exploration, and validated design to prevent wasted implementation effort.

What are the limitations of skipping the specification phase in software planning?▼

Skipping the specification phase in software planning limits your ability to catch scope creep and wasted implementation effort. Without incremental validation of design sections, you risk building features that fail to meet actual user intent and constraints.