codify-to-knowhow

Convert manifest-driven packages into ref-linked knowhow files and spec entries.

76|5|Updated Jul 7, 2026

Search Tags:#manifest #knowledge generation #idempotent writing #knowhow #spec entries #ref linking

Ready to run

npx skills add https://github.com/catlog22/pi-maestro-flow --skill codify-to-knowhow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codify-to-knowhow
Source: https://github.com/catlog22/pi-maestro-flow/tree/main/.pi/skills/codify-to-knowhow
Command: npx skills add https://github.com/catlog22/pi-maestro-flow --skill codify-to-knowhow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill converts a structured manifest into persistent knowhow and spec entries, removing the manual work of writing, organizing, and linking reusable knowledge assets.

Core Features & Use Cases

Manifest-driven generation: Reads a knowhow-manifest.json file and creates the corresponding knowhow documents and spec entries.
Ref-linked knowledge structure: Builds a bridge between concise spec entries and detailed knowhow files using ref links.
Idempotent knowledge writing: Skips assets that already exist so the workflow can be rerun safely without duplicating content.
Use case: After a style, design, or engineering package is codified into a manifest, use this Skill to publish it into the maestro knowledge system.

Quick Start

Ask the assistant to run codify-to-knowhow on the package directory so it can read the manifest and write the generated knowledge assets.

Frequently Asked Questions about codify-to-knowhow

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

FAQPage Schema

How do I convert a manifest into persistent knowhow and spec entries?▼

To convert a manifest into persistent knowhow, use a manifest-driven generation process that reads a knowhow-manifest.json file and creates corresponding knowhow documents and spec entries with ref-based linking. This removes the manual work of writing and organizing reusable knowledge assets.

What is ref-based linking for spec entries and knowhow files?▼

Ref-based linking builds a bridge between concise spec entries and detailed knowhow files using ref links. This mechanism connects structured project knowledge, such as style guides and design decisions, into a cohesive and reusable maestro knowledge system.

Can I rerun manifest-driven knowledge generation without duplicating files?▼

Yes, you can safely rerun manifest-driven knowledge generation because it uses idempotent file creation. The process skips assets that already exist, preventing content duplication and ensuring the workflow can be executed repeatedly without overwriting or duplicating knowhow.

Does codify-to-knowhow require validating the knowhow-manifest.json file?▼

Yes, codify-to-knowhow requires validation of the knowhow-manifest.json file before generating assets. This validation step ensures the manifest structure is correct, enabling accurate idempotent file creation and spec entry generation for your style or design package.

When do I need to codify structured project knowledge into reusable assets?▼

You need to codify structured project knowledge when a style, design, or engineering package must be published into a reusable knowledge system. This applies to workflows that require design decisions or style guides converted into persistent knowhow files and spec entries.