Skills Guide

Specification Documentation

VerifiedSafe

Generates specification Markdown files in the specs/ directory to document recently completed work. Use it after implementing features, changing architecture, or creating immersive experiences to structure technical documentation.

Download and use
Sby Skills Guide Bot
DocumentationIntermediate
6/2/2026
Claude Code
#documentation#specification#code-documentation#project-documentation#workflow

Recommended for

Claude CodeAuto documentationProductivity

Automated summary

Creates Markdown specification files in a specs/ directory to document recently completed work during a session.

Strengths

  • Automates post-development documentation
  • Clear structure with standardized sections
  • Supports various types (features, architecture, immersive)
  • Auto-updates related README files

Limitations

  • Requires a meaningful conversation history to extract details
  • Does not cover pre-existing code outside the session
When to use it

At the end of a development session to capture implementation decisions and details.

When not to use it

If no significant work was done or if documentation is maintained in an external tool.

Security analysis

Safe
Quality score85/100

The skill only provides instructions for the AI to generate documentation files; it does not execute commands, manipulate sensitive data, or interact with external systems.

No concerns found

How this analysis is made

Examples

General spec creation
/spec
Named feature spec
/spec user-authentication
Immersive experience spec
/spec immersive

name: spec description: Document recently completed work by creating spec .md files in specs/ directory

/spec - Document Recently Completed Work

Create specification documentation for recently completed work in this session.

Instructions

When the user invokes /spec, you should:

  1. Review the conversation to identify what was recently built, fixed, or modified

  2. Determine the appropriate spec type based on the work:

    • Immersive experience → Create in specs/immersive/
    • New feature/flow → Create in specs/features/
    • Architecture change → Update specs/architecture.md
    • General spec → Create in specs/

  3. Create the spec file with this structure:

    # [Feature Name]

**File(s):** `path/to/file.swift`
**Type:** [View | Manager | Component | Flow]
**Purpose:** One-line description

---

## Overview
Brief description of what this does and why it exists.

## Implementation
Key code patterns, setup, and usage.

## Integration Points
How this connects to other parts of the codebase.

## Usage Example
Code snippets showing how to use this feature.

  4. For immersive/RealityView specs, include:

    • RealityView structure (content, update, attachments)
    • 3D entities created/modified
    • ARKit integration (hand tracking, image tracking)
    • Collision detection setup
    • Attachment positions and sizes

  5. Update the relevant README.md if adding to a subdirectory

Arguments

  • /spec [name] - Create spec with specific name
  • /spec immersive - Force creation in specs/immersive/
  • /spec update - Update existing spec files based on recent changes

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/specification-documentation-mm78nnuq/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/specification-documentation-mm78nnuq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/specification-documentation-mm78nnuq/download' --output '.skill-downloads/specification-documentation-mm78nnuq/SKILL.md.part' && mv '.skill-downloads/specification-documentation-mm78nnuq/SKILL.md.part' '.skill-downloads/specification-documentation-mm78nnuq/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/specification-documentation-mm78nnuq/SKILL.md' && test -s '.skill-downloads/specification-documentation-mm78nnuq/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/spec' && cp -R '.skill-downloads/specification-documentation-mm78nnuq' '.claude/skills/spec'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/specification-documentation-mm78nnuq'

openskills read 'specification-documentation-mm78nnuq'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/specification-documentation-mm78nnuq/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Supabase Docs Authoring

Documentation

Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.

Claude CodeintermediateSafe 108,544
Skills Guide Bot

Create Architecture Decision Record

Documentation

Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.

Claude CodeintermediateSafe 69,659
Skills Guide Bot

Plan update with deep research

Documentation

Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.

Claude CodeadvancedSafe 248,015
Skills Guide Bot