Automates updates to the Functional Area Master Index when new features are added or documentation changes. Maintains the single navigation source for all feature documentation, ensuring discoverability and organization.
Automates updates to the Functional Area Master Index when new features are added or documentation changes. Maintains the single navigation source for all feature documentation, ensuring discoverability and organization.
/plugin marketplace add DarkMonkDev/WitchCityRope/plugin install darkmonkdev-witchcityrope-agents@DarkMonkDev/WitchCityRopeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Purpose: Automate updates to Functional Area Master Index when features or documentation change.
When to Use: After creating new functional area documentation or completing feature work.
Problem: Documentation scattered across /docs/functional-areas/ becomes undiscoverable.
Solution: Single navigation index at /docs/architecture/functional-area-master-index.md
Result: All documentation discoverable, organized by domain, with status tracking.
Location: /docs/architecture/functional-area-master-index.md
Organization:
# Functional Area Master Index
## Core System
- Authentication & Authorization
- User Management
- Profile Management
## Events Domain
- Event Management
- Session Management
- Registration System
## Content & Community
- Teacher Bios
- Event Catalog
- Venue Management
## Operations
- Safety & Reporting
- Payment Processing
- Communication System
[For each area:]
## Feature Name
**Domain**: Core System | Events | Content | Operations
**Status**: Active | Deprecated | Planned
**Owner**: Team/Agent
**Last Updated**: YYYY-MM-DD
### Documentation
- [Business Requirements](./path/to/requirements.md)
- [Functional Spec](./path/to/functional-spec.md)
- [API Documentation](./path/to/api-docs.md)
### Key Files
- Feature Code: `/apps/web/src/features/feature-name/`
- API Endpoints: `/apps/api/Features/FeatureName/`
- Tests: `/tests/playwright/feature-name*.spec.ts`
### Related Areas
- [Related Feature 1](#feature-1)
- [Related Feature 2](#feature-2)
When new feature is completed:
When feature changes:
When new docs created:
When functional areas restructure:
# Add new feature to index
bash .claude/skills/master-index-updater/execute.sh \
add \
"Streamlined Check-in Workflow" \
"Events Domain" \
"docs/functional-areas/events/new-work/2025-11-03-streamlined-checkin-workflow"
# Update existing feature timestamp
bash .claude/skills/master-index-updater/execute.sh \
update \
"Event Management" \
"" \
""
# Mark feature as deprecated
bash .claude/skills/master-index-updater/execute.sh \
deprecate \
"Legacy Registration System" \
"" \
""
# Show help and usage information
bash .claude/skills/master-index-updater/execute.sh --help
Use the master-index-updater skill to add [feature-name] to the index
After organizing feature documentation (librarian):
bash .claude/skills/master-index-updater/execute.sh \
add \
"New Feature Name" \
"Core System" \
"docs/functional-areas/auth/new-feature"
When deprecating old feature:
bash .claude/skills/master-index-updater/execute.sh \
deprecate \
"Old Feature Name" \
"" \
""
After organizing feature documentation, I'll use the master-index-updater skill to add the feature to the index.
# Add new feature
bash .claude/skills/master-index-updater.md \
add \
"Streamlined Check-in Workflow" \
"Events Domain" \
"docs/functional-areas/events/new-work/2025-11-03-streamlined-checkin-workflow"
# Update feature timestamp
bash .claude/skills/master-index-updater.md \
update \
"Event Management" \
"" \
""
# Mark feature as deprecated
bash .claude/skills/master-index-updater.md \
deprecate \
"Legacy Registration System" \
"" \
""
Characteristics:
Examples:
Characteristics:
Examples:
Characteristics:
Examples:
Characteristics:
Examples:
### Feature Name
**Domain**: [Core System | Events Domain | Content & Community | Operations]
**Status**: [✅ Active | ⚠️ Deprecated | 🔵 Planned | 🚧 In Progress]
**Owner**: WitchCityRope Team
**Last Updated**: YYYY-MM-DD
#### Documentation
- [Business Requirements](./path/to/business-requirements.md)
- [Functional Spec](./path/to/functional-spec.md)
- [Database Design](./path/to/database-design.md)
- [UI/UX Design](./path/to/ui-ux-design.md)
- [Implementation Notes](./path/to/implementation-notes.md)
- [Testing Notes](./path/to/testing-notes.md)
#### Key Files
- Feature Code: `/apps/web/src/features/feature-name/`
- API Endpoints: `/apps/api/Features/FeatureName/`
- Database: `/apps/api/Data/Entities/FeatureName.cs`
- Tests: `/tests/playwright/feature-name*.spec.ts`
#### Related Areas
- [Related Feature 1](#related-feature-1)
- [Related Feature 2](#related-feature-2)
#### Status Notes
- [Current status description]
- [Known issues or limitations]
- [Migration notes if deprecated]
---
Librarian is responsible for:
Workflow:
Problem: Feature added to wrong domain Impact: Confusing navigation Solution: Move entry to correct domain, update related links
Problem: Links point to non-existent files Impact: Users can't find documentation Solution: Validate links before adding, fix broken links
Problem: Feature added multiple times Impact: Confusing navigation Solution: Check for existing entry before adding
Problem: Deprecated features not marked Impact: Users try to use old features Solution: Regular audit, mark deprecated features
{
"masterIndexUpdate": {
"action": "add",
"feature": "Streamlined Check-in Workflow",
"domain": "Events Domain",
"status": "Active",
"timestamp": "2025-11-04",
"documentation": [
"business-requirements.md",
"functional-spec.md",
"database-design.md",
"ui-ux-design.md"
],
"location": "/docs/architecture/functional-area-master-index.md",
"section": "## Events Domain",
"backup": "/docs/architecture/functional-area-master-index.md.backup"
},
"nextSteps": [
"Verify all documentation links work",
"Add related area cross-references",
"Update PROGRESS.md with new feature"
]
}
Initial Context: Show action and feature name On Request: Show full entry being added/updated On Completion: Show location and backup path On Failure: Show validation errors and required fixes
Remember: The Master Index is the entry point for all feature documentation. Without it, documentation is invisible. With it, every feature is discoverable, organized, and maintainable. This skill automates keeping it current.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.