skills.rest
baekenough
baekenoughCOMMUNITY
Explore all skills by this author →
GitHub

omcustom-takeover

Extract canonical specifications from Claude agents or skills into structured spec documents.

13|6|Updated Apr 14, 2026
Search Tags:#workflow#specification#agent#yaml#skill#frontmatter#reverse-engineer
One-click install
npx skills add https://github.com/baekenough/second-brain --skill omcustom-takeover
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omcustom-takeover
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/omcustom-takeover
Command: npx skills add https://github.com/baekenough/second-brain --skill omcustom-takeover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract canonical specifications from evolved agents or skills by reverse-engineering intents, invariants, workflow contracts, and I/O contracts.

Core Features & Use Cases

  • Read target files from .claude/agents or .claude/skills and parse metadata.
  • Generate a structured spec document at .claude/specs/<name>.spec.md detailing intent, invariants, workflow, I/O, dependencies, and boundaries.
  • Use case: teams migrating undocumented assets can create formal contracts for refactoring and compliance.

Quick Start

Run /omcustom-takeover <agent-name> to generate a formal spec from the target's files.

Frequently Asked Questions about omcustom-takeover

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

FAQPage Schema
How do I reverse-engineer a formal specification from an existing agent or skill?▼

To reverse-engineer a formal specification, use the tool to read target files under .claude/agents or .claude/skills, parse their metadata, and extract canonical specs covering intents, invariants, workflow contracts, and I/O contracts into a structured markdown document.

What is the best way to extract workflow contracts and I/O boundaries from undocumented agents?▼

Extracting workflow contracts and I/O boundaries is achieved by reading the agent or skill content and metadata to identify dependencies, tool usage, and structural limits, generating a formal spec at .claude/specs/<name>.spec.md for safe refactoring.

Can I generate a specification from YAML frontmatter and markdown files in .claude directories?▼

Yes, you can generate a specification from YAML frontmatter and markdown files stored in .claude/agents/<name>.md or .claude/skills/<name>/SKILL.md, reading both metadata and content to build a structured specification.

How do I create formal contracts for refactoring undocumented team assets?▼

Create formal contracts for refactoring by running the extraction process on evolved, undocumented assets to produce a canonical spec that details intent, dependencies, and boundaries, ensuring repeatable and safe code transformations.

Does this specification extraction process require any external dependencies or components?▼

No, the specification extraction process requires zero external dependencies or components, operating directly on local .claude directory files to read metadata and output the generated spec document.

When do I need to derive a canonical spec from an existing agent?▼

You need to derive a canonical spec from an existing agent when migrating undocumented assets, ensuring compliance, or preparing for safe refactoring by formalizing the evolved intents, invariants, and workflow contracts into a structured document.

Related Skills

Explore More Software Engineering Skills→
victorjoshi9victorjoshi9
1

plugin-settings

Manage per-project plugin settings stored in .claude/*.local.md files.

Community
Advanced
windyskywindysky

moai-workflow-ddd

Automate domain-driven refactoring with the ANALYZE-PRESERVE-IMPROVE cycle.

Community
Advanced
hiddink-aihiddink-ai
1

hiddink-harness-takeover

Parse YAML frontmatter and markdown to generate structured .spec.md files.

Official
Intermediate
voidreadervoidreader

spec-pipeline

Orchestrate specification drafting and verification for planning documents.

Community
Advanced