doc-architect

Generate a Documentation Planning checklist for feature planning workflows.

1|2|Updated Sep 17, 2025
One-click install
npx skills add https://github.com/MAdrid1011/Zircon-VLIW --skill doc-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-architect
Source: https://github.com/MAdrid1011/Zircon-VLIW/tree/main/.claude/skills/doc-architect
Command: npx skills add https://github.com/MAdrid1011/Zircon-VLIW --skill doc-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning feature work often results in missing or inconsistent documentation, causing delays and misalignment.

Core Features & Use Cases

  • Generates a structured Documentation Planning checklist covering docs, folder READMEs, and interface docs for new features.
  • Integrates into planning workflows to ensure documentation tasks are visible and assigned.
  • Use case: during feature planning, run the skill to produce a ready-to-import Documentation Planning section for plans.

Quick Start

Summarize the feature requirements and run /doc-architect to generate a Documentation Planning section.

Frequently Asked Questions about doc-architect

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

FAQPage Schema
How do I generate a documentation planning checklist for new feature work?

To generate a documentation planning checklist, summarize feature requirements, affected modules, and new functionality, then run the tool to output a structured Documentation Planning section for your workflows.

What is the best way to ensure READMEs and interface docs are included in feature planning?

The best way to include folder READMEs and interface docs in feature planning is to automate checklist generation, ensuring all documentation tasks are visible, assigned, and integrated before new features roll out.

Can I use this for large-scale refactoring documentation or is it only for new features?

Yes, you can use this for large-scale refactoring documentation as well as new feature rollouts across product, design, and engineering teams to identify and fill missing documentation gaps.

How do I fill documentation gaps caused by inconsistent planning workflows?

You fill documentation gaps by running the skill against conversation context describing feature requirements, which produces a ready-to-import planning section that aligns team documentation tasks.

Does generating a planning checklist require any specific frameworks or dependencies?

No specific frameworks or dependencies are required; the skill relies solely on inputting feature requirements and conversation context to generate the structured planning documentation output.

What inputs do I need to prepare to generate interface docs for a feature rollout?

You need to prepare a summary of feature requirements, affected modules, and new functionality from your conversation context to successfully generate interface docs and planning checklists.