discover-docs-norms

Scan documentation structures and generate artifact norms files after user approval.

7|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/nesnilnehc/ai-cortex --skill discover-docs-norms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discover-docs-norms
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/discover-docs-norms
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill discover-docs-norms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formalizes and enforces project-wide documentation norms by scanning existing docs structures to produce clear, actionable artifact standards for paths, naming, and lifecycle.

Core Features & Use Cases

  • Scan the project's docs/ structure to identify existing workflows for todos, design decisions, ADRs, and calibration artifacts.
  • Interactive start: confirm or adapt the starting template (AI Cortex default, project template, or blank) to map product types to paths.
  • Output generation: create a human-readable docs/ARTIFACT_NORMS.md and optionally a machine-readable .ai-cortex/artifact-norms.yaml.
  • Governance: require user approval before writing to disk to ensure alignment with project needs.

Quick Start

Start by running the discovery flow to scan your project docs/ and generate docs/ARTIFACT_NORMS.md (and optionally .ai-cortex/artifact-norms.yaml) after you approve the proposed norms.

Frequently Asked Questions about discover-docs-norms

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

FAQPage Schema
How do I discover and formalize documentation norms for an existing project?

Discovering documentation norms involves scanning an existing project's docs/ structure to identify current artifact workflows. It maps existing ADRs, todos, and design decisions into a formalized, project-wide standard for paths, naming, and lifecycle management.

What is the best way to generate an artifact norms file for my repository?

The best way to generate an artifact norms file is to run an automated discovery flow that scans your docs/ directory and confirms your starting template. It outputs a human-readable docs/ARTIFACT_NORMS.md and an optional machine-readable .ai-cortex/artifact-norms.yaml only after receiving explicit user approval.

Do I need a specific repository structure to map documentation artifact norms?

You do not need a specific repository structure. The discovery process applies to varied repository structures by scanning the existing docs/ folder to map product types to paths, accommodating AI Cortex default templates, project templates, or blank starting configurations.

Can I use a machine-readable format for project documentation norms?

Yes, you can output project documentation norms in a machine-readable format by generating an optional .ai-cortex/artifact-norms.yaml file. This structured output sits alongside the human-readable docs/ARTIFACT_NORMS.md to support downstream automation skills.