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.

Sby Skills Guide Bot
DocumentationIntermediate
506/2/2026
Claude Code
#documentation#specification#code-documentation#project-documentation#workflow

Recommended for

Our review

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

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
Related skills