project-docs-prep

project-docs-prep is a skill for Claude Code, Codex from ntaffzii/Skill-Agents. It costs 218 tokens per session (1,180 once invoked), scanned A, original, MIT.

A documentation scaffold for software projects that prepares files describing what to build and how an AI coding agent should work in the repository.

In plain words
What is it for?
Preparing project specifications, system requirements, architecture notes, user-interface guidance, README files, and instruction files such as AGENTS.md or CLAUDE.md before coding begins.
Why use it?
It removes the need to organise project requirements, architecture, design guidance, and agent instructions from scratch. It also turns incomplete documentation into a clearer working set.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

Good fit Preparing project specifications, system requirements, architecture notes, user-interface guidance, README files, and instruction files such as AGENTS.md or CLAUDE.md before coding begins.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ntaffzii/skill-agents/project-docs-prep
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ntaffzii/Skill-Agents --skill project-docs-prep
Clone the repo
git clone --depth 1 https://github.com/ntaffzii/Skill-Agents

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for project-docs-prep

README.md
[![agentmods](https://agentmods.dev/badge/skills/ntaffzii/skill-agents/project-docs-prep/github.svg)](https://agentmods.dev/skills/ntaffzii/skill-agents/project-docs-prep)
Your own site
<a href="https://agentmods.dev/skills/ntaffzii/skill-agents/project-docs-prep"><img src="https://agentmods.dev/badge/skills/ntaffzii/skill-agents/project-docs-prep/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for project-docs-prep

Your own site · 80×15
<a href="https://agentmods.dev/skills/ntaffzii/skill-agents/project-docs-prep"><img src="https://agentmods.dev/badge/skills/ntaffzii/skill-agents/project-docs-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 218 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,180 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00218 $0.01180
Opus 5.5 $0.00087 $0.00472
Sonnet 5.5 $0.00044 $0.00236
Haiku 4.5 $0.00022 $0.00118

Measured 1mo ago against content hash 90876b582aac, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

project-docs-prep scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/project-docs-prep/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Docs Prep

Turns a short project idea (or an existing incomplete docs folder) into a complete, AI-agent-ready documentation set. Produces two operational layers:

  1. Spec Layer (docs/) — describes what to build. Five numbered files:
    • 01-project-overview.md
    • 02-system-requirements.md
    • 03-tech-stack-architecture.md
    • 04-system-modeling.md
    • 05-ux-ui-design.md
  2. Operational Layer (repo root) — describes how the agent should work and what design tokens/commands look like:
    • AGENTS.md
    • DESIGN.md
    • CLAUDE.md
    • README.md

These two layers are complementary, not redundant. The spec layer is read once during planning. The operational layer is loaded by the agent every session — keep it concise and omit facts inferable from code.

Templates

This skill ships with skeleton templates in templates/. When generating docs for a new project:

  1. Read the relevant template from templates/ as your starting structure.
  2. Replace all {{PLACEHOLDER}} markers with project-specific content.
  3. Delete any sections that don't apply — do NOT leave empty headings.
  4. Add project-specific sections where the template doesn't cover them.

See references/template-usage-guide.md for detailed instructions on each template.


Workflow

Step 1 — Gather Project Info

If given a short idea (e.g. "Meeting room booking system for 50 users"), do not interrogate field-by-field. Draft reasonable content and mark uncertain items with > ⚠️ TODO:. Only ask clarifying questions when the answer would alter architecture or design direction.

Step 2 — Generate docs/01–05

Create numbered specs in docs/. Use the templates in templates/docs/ as starting structure. Maintain consistent section headings. Fill placeholders with project specifics. Keep descriptions clear and accessible for both human developers and AI agents.

Step 3 — Generate AGENTS.md

Use templates/AGENTS.md as base. Include build, test, and lint commands for the chosen stack, directory layout, and hard constraints. Delete non-applicable template sections to conserve token budget.

Read the full file on GitHub · 85 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 85 lines · 218 tokens per session scan A 90876b582aac

Subscribe to this mod's changes

project-docs-prep is a skill published in the GitHub repository ntaffzii/Skill-Agents (4 stars, last pushed 15d ago), licensed MIT. It adds 218 tokens to every session and 1,180 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

geo-platform-optimizer

Platform-specific AI search optimization — audit and optimize for Google AI Overviews, ChatGPT, Perplexity, Gemini, and Bing Copilot individually.

zubair-trabzada/geo-seo-claude · 34 tokens

pake

Package a website or local web build as a desktop app with Pake. Use for packaging, CLI options, icons, bundle identifiers, or WebView proxy setup. Not for unrelated Tauri development or uninstalling apps.

tw93/Pake · 47 tokens

task

\ You are executing a task within the LobeHub task system. Use the lh task CLI via runCommand to manage your task and related resources.

lobehub/lobehub · 0 tokens

intelli-flows

Use when the user wants to design, draw or build an AI workflow in Python with Intelli (intelli.flow), especially one that mixes providers (OpenAI, Anthropic, Gemini, AWS Bedrock, Mistral, local models) or agent types (assistants with documents, history and memory, image generation, vision, speech, transcription…

intelligentnode/Intelli · 187 tokens

citation-intelligence

Use when the user wants to know which URLs AI engines cite for a query, whether their domain is being cited by ChatGPT/Claude/Perplexity/Gemini/Google AI Overviews/Bing, what queries their site is cited for, how citation rate changes over time, or how their citation coverage compares to competitors. Self-hosted, BYO…

AutomateLab-tech/citation-intelligence · 82 tokens

conductor-setup

Scaffolds the project and sets up the Conductor environment interactively.

vasilistsavalias/conductor_for_codex · 19 tokens