skills.rest
RayOfSteel-DHBW
RayOfSteel-DHBWCOMMUNITY
Explore all skills by this author →
GitHub

discovery-phase

Generate DISCOVERY.md at selected depth levels to guide PLAN.md creation.

Updated Nov 16, 2025
Search Tags:#workflow#planning#templates#documentation#discovery#context7
One-click install
npx skills add https://github.com/RayOfSteel-DHBW/TeilAutoNeu --skill discovery-phase-rayofsteel-dhbw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discovery-phase
Source: https://github.com/RayOfSteel-DHBW/TeilAutoNeu/tree/main/.github/skills/discovery-phase
Command: npx skills add https://github.com/RayOfSteel-DHBW/TeilAutoNeu --skill discovery-phase-rayofsteel-dhbw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes discovery at the appropriate depth level and produces DISCOVERY.md to inform PLAN.md creation, enabling consistent planning across quick, standard, and deep investigations.

Core Features & Use Cases

  • Supports three depth levels (verify, standard, deep) and outputs DISCOVERY.md tailored to each.
  • Integrates with plan-phase.md and repository templates to standardize exploration and decision-making.
  • Useful for architecture, vendor comparison, and technology selection across multiple libraries or tools.

Quick Start

Invoke discovery at the chosen depth (verify, standard, or deep) to generate DISCOVERY.md and guide PLAN.md.

Frequently Asked Questions about discovery-phase

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

FAQPage Schema
How do I structure discovery planning for architecture investigations across multiple libraries?▼

Structured discovery planning automates depth selection and generates a DISCOVERY.md file to guide PLAN.md creation for architecture investigations across multiple libraries.

What is the best way to standardize technology selection and vendor comparison documentation?▼

Standardize technology selection and vendor comparison by generating context-rich DISCOVERY.md with traceable sources, ensuring consistent decision-making across different depth levels.

Can I use discovery templates for quick state verification instead of deep architectural research?▼

Yes, discovery templates support three depth levels including quick verify for state verification, alongside standard decision-making and deep architectural investigations.

How does discovery phase output integrate with downstream repository planning templates?▼

Discovery phase output integrates directly with plan-phase.md and repository templates, producing DISCOVERY.md to inform and guide subsequent PLAN.md creation and standardize exploration.

Do I need explicit depth handling when planning discovery workflows for multiple tools?▼

Explicit depth handling is required when planning discovery workflows for multiple tools to satisfy requirements for context-rich findings and traceable sources across varying investigation scopes.

Why does discovery planning separate verify, standard, and deep investigation levels?▼

Discovery planning separates verify, standard, and deep investigation levels to execute exploration at the appropriate depth, preventing over-analysis for quick checks while enabling comprehensive multi-library research.

Related Skills

Explore More Product & Management Skills→
kireevkit15-syskireevkit15-sys

shape

Run a structured discovery interview and generate a design brief.

Community
Advanced
virtenginevirtengine
17

discovery-phase

Automate discovery workflows to generate DISCOVERY.md for planning.

Official
Advanced
yongwoonyongwoon
8

ywc-tech-research

Compare software libraries and architectural approaches with verifiable documentation.

Community
Advanced
KbediakoKbediako
3

collab-deliberation

Structure multi-agent brainstorming into a five-step deliberation workflow.

Community
Basic