seed

Scan signals, evaluate gaps, and build cabinet SKILL.md files.

Updated Aug 27, 2026

Search Tags:#collaboration #onboarding #governance #phases #expertise #cabinet #seed

Ready to run

npx skills add https://github.com/orenmagid/claude-cabinet --skill seed-orenmagid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: seed
Source: https://github.com/orenmagid/claude-cabinet/tree/main/templates/skills/seed
Command: npx skills add https://github.com/orenmagid/claude-cabinet --skill seed-orenmagid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Seed solves the problem of systematically building and maintaining a tailored cabinet of domain experts for a project. Activated during seed to recruit new cabinet members. It helps teams ensure expertise is available when needed, rather than reactive hiring after incidents.

Core Features & Use Cases

Phase-driven workflow: scan signals, evaluate gaps, and build new cabinet members in a coherent sequence.
Collaborative authoring: teams co-create cabinet SKILL.md templates that reflect project-specific risks and governance.
Lifecycle alignment: integrates with committees and the cabinet lifecycle guidance to keep coverage up to date.

Quick Start

Run /seed to detect gaps, evaluate coverage, and collaboratively build cabinet members for your project.

Frequently Asked Questions about seed

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

FAQPage Schema

How do I build a team of domain experts for a new software project?▼

Building a team of domain experts involves scanning project signals, evaluating coverage gaps, and collaboratively authoring expert profiles. This phase-driven approach ensures expertise is proactively recruited during onboarding rather than reactively added after incidents.

What is the best way to maintain project expertise coverage as technology evolves?▼

Maintaining project expertise coverage requires ongoing evaluation of technical signals and risk gaps against existing domain experts. A collaborative lifecycle process updates expert profiles to keep governance and technical alignment current throughout development.

How do I identify gaps in my project's domain expertise during onboarding?▼

Identifying domain expertise gaps during onboarding involves scanning project signals and evaluating existing coverage. This detects missing technical knowledge and governance requirements, allowing teams to target and build specific expert profiles.

Can I co-create custom expert profiles with governance hooks for my team?▼

Yes, you can co-create custom expert profiles with governance hooks. Teams collaboratively author standardized template files that reflect project-specific risks and integrate with committee lifecycle guidance to manage domain expertise.

Does collaborative cabinet creation work with ongoing development phases?▼

Collaborative cabinet creation works with ongoing development phases by applying a phase-driven workflow. It continuously scans signals and evaluates gaps to keep domain expertise aligned with evolving technology and project risks.

Why use a phase-driven workflow for building domain expertise instead of hiring reactively?▼

A phase-driven workflow for building domain expertise prevents knowledge gaps by systematically scanning signals and evaluating coverage. This proactive approach ensures expertise is available before incidents occur, unlike reactive hiring.