docs-organize

Generate standardized project documentation and 0-100 health scores from codebases.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/s0613/S-skills --skill docs-organize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-organize
Source: https://github.com/s0613/S-skills/tree/main/docs-organize
Command: npx skills add https://github.com/s0613/S-skills --skill docs-organize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Project documentation is often inconsistent, incomplete, or outdated, leading to poor team collaboration, slow onboarding, and unclear project context. This Skill eliminates that manual overhead by automatically generating a complete, standardized documentation structure and objective project health score for any codebase.

Core Features & Use Cases

  • Codebase Analysis: Automatically infers tech stack, project type, existing architectural decisions, and current project stage from existing code and configuration files.
  • Contextual Gap Interview: Asks targeted user questions to fill missing context that cannot be inferred from code alone, ensuring generated docs are accurate and complete.
  • Standardized Doc Generation: Produces a full docs/ structure including prd.md, architecture.md, UI_GUIDE.md (for frontend projects), STATUS.md with a 0-100 health score, and ADRs for key architectural decisions.
  • Use Case: A small startup team with a scattered codebase and no formal documentation can run this Skill to get a complete, standardized docs package and a clear score to track project health over time.

Quick Start

Invoke the docs-organize skill by typing /docs-organize in any project directory to generate your standardized project documentation and health score.

Frequently Asked Questions about docs-organize

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

FAQPage Schema
How do I auto-generate project documentation for an existing codebase?

Automated project documentation generation analyzes your existing codebase to infer the tech stack, asks targeted interview questions to fill missing context, and outputs a standardized docs structure including prd.md, architecture.md, and ADRs.

What is a project health score and how is it calculated for software codebases?

A project health score is an objective 0-100 metric generated by analyzing your codebase and contextual information. It is documented in STATUS.md to help teams collaboratively track project maintainability over time.

Can I generate architectural decision records automatically for any project type?

Yes, you can generate architectural decision records automatically for any project type including web apps, APIs, CLIs, mobile apps, and libraries. The skill infers existing architectural decisions directly from your code.

What's the best way to standardize inconsistent project documentation across a startup team?

The best way to standardize inconsistent project documentation is to run an automated generation skill that produces a uniform docs structure and objective health scores, thereby eliminating manual overhead and improving team onboarding.

Does automated documentation generation work without existing configuration files?

Automated documentation generation can analyze existing code and configuration files to infer context, but if configuration files are missing, the skill conducts targeted contextual gap interviews with the user to ensure accurate and complete documentation.

When do I need to manually answer questions during the documentation generation process?

You need to manually answer questions during documentation generation when the codebase analysis cannot infer missing contextual information. The skill asks targeted interview questions to fill these specific gaps for documentation accuracy.