doc-architect

Name: doc-architect
Availability: InStock
Author: Ayazhan

Generate documentation impact checklists for new features against design docs and READMEs.

Updated Feb 9, 2026

Search Tags:#code review #documentation #checklist #feature planning #design docs #interface docs

Ready to run

npx skills add https://github.com/ayazhankadessova/essential-skills --skill doc-architect-ayazhankadessova

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-architect
Source: https://github.com/ayazhankadessova/essential-skills/tree/main/plugins/essential-skills/skills/doc-architect
Command: npx skills add https://github.com/ayazhankadessova/essential-skills --skill doc-architect-ayazhankadessova

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the identification of all documentation files that need to be created or updated when a new feature is introduced, ensuring comprehensive documentation coverage.

Core Features & Use Cases

Impact Analysis: Scans a feature's scope to determine necessary documentation updates across design docs, folder READMEs, and interface docs.
File Path Generation: Lists concrete file paths for each documentation artifact, specifying whether it's a new creation or an update.
Use Case: Before implementing a new authentication flow, use this skill to generate a checklist of all design documents, API documentation, and relevant READMEs that need to be written or modified.

Quick Start

Run the doc-architect skill to generate a documentation impact checklist for the new real-time notifications feature.

Frequently Asked Questions about doc-architect

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

FAQPage Schema

How do I identify which documentation files need updating when adding a new feature?▼

To identify documentation files needing updates, analyze the new feature's scope against design docs, folder READMEs, and interface docs. This process generates an impact checklist specifying exact file paths to create or update with rationales for comprehensive coverage.

What is the best way to plan documentation updates for a new authentication flow?▼

The best way to plan documentation updates is running an automated impact analysis on the feature scope. It lists all design documents, API documentation, and relevant READMEs requiring modification or creation before implementation begins.

How do I generate a checklist of design docs and interface docs for a new software feature?▼

Generate a checklist by analyzing the feature's scope to determine necessary updates across design docs, folder READMEs, and interface docs. The output provides specific file paths for each documentation artifact with rationales for structured planning.

Can I use this documentation planning approach for any new software feature implementation?▼

Yes, you can use this documentation impact analysis approach for any new software feature. It works by evaluating the feature scope against existing documentation structures to produce a tailored checklist of files to create or update.

Why does my team miss updating folder READMEs and interface docs during feature planning?▼

Teams miss updating folder READMEs and interface docs because feature planning lacks structured impact analysis. Automating the identification of necessary documentation updates across design docs and READMEs ensures comprehensive coverage before implementation.