agentdev-design-file-manager

Manages Design file creation, appending, and target_area section replacement with lifecycle status rules.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-design-file-manager-yogata
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentdev-design-file-manager
Source: https://github.com/yogata/agent-dev-flow/tree/main/src/opencode/skills/agentdev-design-file-manager
Command: npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-design-file-manager-yogata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typescript, @types/bun, and includes scripts (resource) and references (resource) components.

What problem does it solve? Managing Design documents in an AI-driven development workflow requires consistent rules for creating new files, appending sections, and replacing existing sections by heading, plus correct draft/accepted lifecycle handling. This Skill centralizes those rules and provides a deterministic script for heading search so section replacement does not depend on LLM guesswork. ## Core Features & Use Cases - Three Operation Modes: CREATE new Design files with complete frontmatter (title, status: draft, created, updated), APPEND sections to existing Designs, and UPDATE sections via target_area heading matching. - Deterministic target_area Search: The bundled TypeScript script search-target-area.ts finds matching Markdown headings across Design files and returns JSON results, with defined behavior for multiple matches (warning) and no matches (skip with follow-up). - Lifecycle and Placement Rules: Applies draft/accepted status rules, resolves placement for new versus existing Designs, and checks ADF-COVERS declaration blocks during design-save. - Use Case: During a case-ready workflow, an agent needs to update the "Error Handling" section of an existing Design document. The Skill locates the exact heading via the script, replaces only that section, and preserves the document's existing status. ## Quick Start Ask the agent to update the target_area section of a Design document under docs/designs using the design file manager rules and its search-target-area script.

Frequently Asked Questions about agentdev-design-file-manager

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

FAQPage Schema
How do I replace a specific section in a Markdown design document?▼

Use the UPDATE operation with a target_area value naming the heading text. The search-target-area.ts script finds the matching heading, the section spans until the next same-or-higher-level heading, and that range is replaced with the new content.

How do I run the search-target-area script?▼

Run it with bun, passing the target_area string and one or more Design file paths as arguments, or pipe JSON with target_area and files fields via stdin. Results are printed to stdout as JSON containing a matches array with file, line, and text.

What happens when target_area matches multiple headings?▼

The script returns all matches in the JSON output, and the calling Design save process rejects the replacement and emits a warning. Replacement only proceeds on a single unambiguous match.

What happens if the target_area heading is not found?▼

The script returns an empty matches array without an error. The calling process skips that action and reports a follow-up recommending switching the operation to create, rather than aborting the whole run.

Does this Skill handle REQ or Decision file operations?▼

No. REQ numbering and file operations belong to agentdev-req-file-manager, and Decision operations belong to agentdev-decision-file-manager. This Skill is scoped strictly to Design files and delegates common validation to agentdev-artifact-validation.