vibeos-discover

Name: vibeos-discover
Availability: InStock
Author: Chieflatif

Identify project context and create discovery artifacts from existing code and docs.

2|1|Updated Mar 9, 2026

Search Tags:#planning #architecture #codebase #discovery #governance #product-definition

Ready to run

npx skills add https://github.com/chieflatif/vibeos-plugin --skill vibeos-discover

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vibeos-discover
Source: https://github.com/chieflatif/vibeos-plugin/tree/main/plugins/vibeos/reference/codex/skills/vibeos-discover
Command: npx skills add https://github.com/chieflatif/vibeos-plugin --skill vibeos-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams anchor discovery for VibeOS projects, providing a clear baseline of governance artifacts, product context, and architectural direction before planning.

Core Features & Use Cases

Read and anchor project context to determine whether a project is greenfield or midstream.
Create or refresh foundational discovery artifacts (config.json, project-definition.json, docs/product/PRODUCT-BRIEF.md, docs/product/PRD.md, docs/product/ARCHITECTURE-OUTLINE.md, docs/TECHNICAL-SPEC.md, and governance artifacts) and keep discovery evidence-backed with explicit assumptions and confidence.
If code exists, anchor discovery in what is present and hand off to vibeos-plan when ready to sequence work orders.

Quick Start

Describe your project goals and let vibeos-discover generate foundational discovery artifacts.

Frequently Asked Questions about vibeos-discover

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

FAQPage Schema

How do I generate product discovery artifacts from an existing codebase?▼

To generate product discovery artifacts from a codebase, this Skill reads your repository context and creates evidence-backed files like PRODUCT-BRIEF.md, PRD.md, and ARCHITECTURE-OUTLINE.md anchored to actual code. It ensures outputs include explicit assumptions and confidence levels.

What is the best way to define project architecture before planning development?▼

Defining project architecture before planning requires establishing a baseline of governance artifacts and product context. This Skill produces foundational docs like TECHNICAL-SPEC.md and project-definition.json, anchoring architectural direction to existing code before sequencing work.

How do I determine if a project is greenfield or midstream for product planning?▼

To determine if a project is greenfield or midstream for product planning, this Skill analyzes your repository to identify project context. It then creates or refreshes discovery artifacts based on whether existing code is present or the project is starting fresh.

Can I create governance artifacts and a PRD from existing repository documentation?▼

Yes, you can create governance artifacts and a PRD from existing repository documentation. This Skill reads current code and docs to produce evidence-backed product definitions, ensuring recommendations are anchored in existing structure before proposing new governance files.

What foundational documents do I need to anchor discovery for a new software project?▼

Foundational documents needed to anchor discovery include config.json, project-definition.json, PRODUCT-BRIEF.md, PRD.md, ARCHITECTURE-OUTLINE.md, and TECHNICAL-SPEC.md. This Skill generates these artifacts with explicit assumptions to provide clear architectural direction.