edi-project

Create or update book project.yaml metadata with validated fields.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Telepotch/hirano-edi-on-claude-code --skill edi-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edi-project
Source: https://github.com/Telepotch/hirano-edi-on-claude-code/tree/main/.claude/skills/edi-project
Command: npx skills add https://github.com/Telepotch/hirano-edi-on-claude-code --skill edi-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables users to create or update the book project's project.yaml metadata file, ensuring consistent structure across projects, including slug, title, author, status, and optional fields.

Core Features & Use Cases

  • Create new project.yaml by deriving fields from existing project artifacts (concept.md, blueprint.md, index.md) and validating required fields.
  • Update individual fields (slug, title, author, status, version, target) without rewriting the entire file.
  • Auto-fill sensible defaults by inspecting project artifacts and enforce a valid status progression.
  • Validate slug consistency with the directory name and ensure status values are within the allowed enum.

Quick Start

Provide the project slug, title, author, and initial status to generate or update projects/{name}/project.yaml.

Frequently Asked Questions about edi-project

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

FAQPage Schema
How do I generate a project.yaml metadata file for my book project?

Generate a project.yaml metadata file by providing the project slug, title, author, and initial status. The skill derives fields from existing project artifacts like concept.md, blueprint.md, and index.md, validates required fields, and produces a clean YAML file.

Can I update individual metadata fields in YAML without rewriting the entire file?

Yes, you can update individual fields in YAML without rewriting the entire file. The skill allows targeted updates to slug, title, author, status, version, and target fields while preserving the rest of the existing metadata structure.

What is metadata validation for a book project and how does it work?

Metadata validation checks that required YAML fields exist and conform to constraints. The skill enforces slug consistency with the directory name and ensures the status field contains values within an allowed enum, producing a clean and consistent project metadata file.

Do I need existing project artifacts to create a project.yaml file?

Existing project artifacts are used to auto-fill sensible defaults but are not strictly required. You can provide the project slug, title, author, and initial status directly to generate or update the project.yaml metadata file.

What are the limitations of automated YAML metadata generation for book projects?

The main limitation is that the skill enforces strict constraints: the slug must match the directory name, and the status must be within an allowed enum. It focuses on metadata structure and validation rather than content creation.