# Documentation Start

> Initialize Memory Bank and Document Hub if not already set up. Use when Codex should run the converted documentation-start workflow. Inputs: force.

- Skill: `artsmc/documentation-start` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add artsmc/documentation-start`
- Raw SKILL.md: https://api.skillmd.com/api/skills/artsmc/documentation-start/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: artsmc (https://skillmd.com/u/artsmc)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/artsmc/documentation-start

---


# Documentation Start

Converted Claude skill workflow for Codex/OpenAI use.

## Source

Converted from `skills/documentation-start/SKILL.md`.

## Converted Instructions

The content below was adapted from the Claude source. Rewrite tool and runtime assumptions as needed when they refer to Claude-only features.

# documentation-start Skill

Initialize project documentation systems (Memory Bank + Document Hub) if needed.

## Usage

```bash
$documentation-start           # Initialize if needed
$documentation-start --force   # Force re-initialization
```

## What It Does

1. **Check Memory Bank Status**
   - Check if `memory-bank/` directory exists
   - Check if all 6 core files present:
     - projectbrief.md
     - productContext.md
     - techContext.md
     - systemPatterns.md
     - activeContext.md
     - progress.md

2. **Check Document Hub Status**
   - Check if `documentation hub directory/` directory exists
   - Check if all 4 core files present:
     - systemArchitecture.md
     - keyPairResponsibility.md
     - glossary.md
     - techStack.md

3. **Initialize If Needed**
   - If Memory Bank missing → Call `$memory-bank-initialize`
   - If Document Hub missing → Call `$document-hub-initialize`
   - If both exist → Report "Already initialized ✅"

4. **Force Mode**
   - If `--force` flag provided:
     - Always call both initialize skills
     - Overwrites existing files

## Workflow Logic

```
START
  ↓
Check memory-bank/ exists?
  ├─ NO → Call $memory-bank-initialize
  └─ YES → Validate 6 files present
      ├─ Valid → Skip Memory Bank ✅
      └─ Invalid → Call $memory-bank-initialize
  ↓
Check documentation hub directory/ exists?
  ├─ NO → Call $document-hub-initialize
  └─ YES → Validate 4 files present
      ├─ Valid → Skip Document Hub ✅
      └─ Invalid → Call $document-hub-initialize
  ↓
Report initialization status
  ↓
END
```

## Output

```
🔍 Checking documentation systems...

Memory Bank:
  ✅ Already initialized (6/6 files present)

Document Hub:
  ⚠️ Not initialized
  🚀 Initializing Document Hub...
  ✅ Document Hub initialized (4/4 files created)

📊 Summary:
  Memory Bank: ✅ Ready
  Document Hub: ✅ Ready

Next steps:
  - Run $feature-new to start a new feature
  - Or use individual skills as needed
```

## When to Use

- **First time in a project**: Always run this first
- **New team members**: Ensures documentation is initialized
- **After cloning repository**: Sets up local documentation
- **Force re-init**: Use `--force` to rebuild documentation

## Implementation Details

This skill uses the Skill tool to invoke:
- `$memory-bank-initialize` (if needed)
- `$document-hub-initialize` (if needed)

No direct file manipulation - delegates to existing skills.