skills.rest
Thawatchai-Petkaew
Thawatchai-PetkaewCOMMUNITY
Explore all skills by this author →
GitHub

discover

Transform ambiguous requirements into actionable specifications with research and gap closure.

Updated Jan 10, 2026
Search Tags:#codebase analysis#gap closure#specification creation#requirement research#story ticket
One-click install
npx skills add https://github.com/Thawatchai-Petkaew/campvibe --skill discover-thawatchai-petkaew
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/Thawatchai-Petkaew/campvibe/tree/main/.claude/skills/discover
Command: npx skills add https://github.com/Thawatchai-Petkaew/campvibe --skill discover-thawatchai-petkaew

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill assists in transforming raw, ambiguous requirements into buildable specifications by facilitating thorough research and gap closure, ensuring clear and actionable specifications before code implementation.

Core Features & Use Cases

  • Requirement Research: Provides a structured approach to research codebases and existing documentation.
  • Gap Closure: Assists in identifying and closing gaps across multiple dimensions (Business, Functional, Technical, UX, Security/Data, Risk).
  • Spec Creation: Outputs a comprehensive story ticket with acceptance criteria based on the closed gaps.
  • Use Case: When starting a new project with unclear requirements, use this Skill to create a detailed ticket that can be confidently taken to the next phase of development.

Quick Start

Run the 'discover' skill to initiate the discovery loop for a new feature.

Frequently Asked Questions about discover

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

FAQPage Schema
How do I transform ambiguous requirements into actionable specifications?▼

To transform ambiguous requirements into actionable specifications, use a structured discovery loop that researches the codebase, identifies documentation gaps, and generates comprehensive story tickets with acceptance criteria.

What dimensions should I cover during requirement research and gap closure?▼

Requirement research and gap closure should cover six critical dimensions: Business, Functional, Technical, UX, Security/Data, and Risk, ensuring comprehensive specification coverage before development begins.

How do I create a story ticket with acceptance criteria from unclear project requirements?▼

To create a story ticket with acceptance criteria from unclear requirements, guide the discovery process through codebase analysis and gap identification across multiple dimensions before outputting the final specification.

Do I need an existing codebase structure to analyze gaps and create specifications?▼

Yes, creating specifications requires a structured understanding of the codebase and existing documentation to effectively research, identify gaps, and close them across all critical requirement dimensions.

What is the best way to stop guessing during specification creation for new features?▼

The best way to stop guessing during specification creation is to facilitate thorough requirement research and gap closure, ensuring clear and actionable specifications are built before code implementation starts.

Related Skills

Explore More Software Engineering Skills→
telum-aitelum-ai
2

project-import

Create a Speck project structure with a skeleton project.md file.

Official
Basic
larus-perituslarus-peritus

Task Planning

Break down approved designs into structured implementation tasks with requirements traceability.

Community
Intermediate
cody-hutsoncody-hutson

pmo-process-designer

Convert business input into structured, traceable requirements and process documentation.

Community
Advanced
hg-pyunhg-pyun
2

interview

Convert ambiguous requests into actionable specifications via interactive clarification.

Community
Advanced