discovery-to-inventory

Coordinate discovery outcomes into persistent inventory entries with glossary terms and a traceable baseline.

20|3|Updated May 14, 2026
One-click install
npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill discovery-to-inventory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discovery-to-inventory
Source: https://github.com/cyberAlchemyAI/Arcanum/tree/main/.claude/skills/discovery-to-inventory
Command: npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill discovery-to-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovery To Inventory turns scattered discovery outputs into persistent, reusable knowledge, preventing loss of context and enabling evidence-backed decisions.

Core Features & Use Cases

  • Build a discovery baseline via scope-interview to capture project scope and initial understanding.
  • Create a glossary to clarify local vocabulary and map terms to reusable inventory entries.
  • Persist decisions, sources, and gaps by updating inventory for future reuse.

Quick Start

Run the discovery-to-inventory workflow on your project idea to generate an initial discovery baseline, glossary, and inventory entries.

Frequently Asked Questions about discovery-to-inventory

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

FAQPage Schema
How do I capture project scope and build a reusable knowledge base from vague discovery outcomes?

Create a discovery baseline by capturing project scope and initial understanding, then map local vocabulary into glossary terms and persist decisions as inventory entries to prevent loss of context across brownfield projects.

How do I create a glossary from unclear project terms during the discovery phase?

Create a glossary by clarifying local vocabulary discovered during scope-interviews, then mapping those terms to reusable inventory entries that form a traceable baseline for future project reuse.

What is the best way to document evidence and decisions for a brownfield project with unclear scope?

Document evidence and decisions by running a structured discovery-to-inventory workflow that enforces explicit inputs and validated gates, producing an inventory report and a traceable baseline for future reuse.

Can I use this discovery workflow for vague ideas and unclear scopes, or does it require a fully defined project?

You can use this discovery workflow directly on vague ideas and unclear scopes without requiring a fully defined project upfront, as it captures initial understanding through a structured scope-interview process.

When should I not use a discovery-to-inventory workflow for knowledge capture?

Avoid using a discovery-to-inventory workflow when your project already has a fully defined, validated scope, as the enforced gates and scope-interviews are designed to resolve ambiguity rather than document known certainties.