nexus-a1/rebuild-requirements-index

Rebuild Requirements Index

Rebuild the search index for the team's requirements repository.

Purpose

Fix corrupted, outdated, or missing index.json file that enables fast search of archived requirements.

When to Use

• Index file corrupted (invalid JSON)
• Search failing or returning incorrect results
• After manual changes to requirements repository
• Index out of sync with actual requirements
• After repository cleanup or archival
• As part of maintenance routine

How It Works

The index provides fast search without reading all requirement files:

Without index:

• Search must read 100+ requirements.md files
• Slow (10+ seconds)
• High memory usage

With index:

• Search reads single index.json file
• Fast (< 100ms)
• Low memory usage

What Gets Rebuilt

The index contains:

• List of all tickets with metadata
• Tag frequencies (for browsing)
• Component frequencies (for filtering)
• Project counts (for multi-project repos)
• Last updated timestamp

Process

Step 1: Check Configuration

Read project configuration:

# Source resolve-config: marketplace installs get ${CLAUDE_PLUGIN_ROOT} substituted
# inline before bash runs; ./install.sh users fall back to ~/.claude. If neither
# path resolves, fail loudly rather than letting resolve_artifact be undefined.
if [ -f "${CLAUDE_PLUGIN_ROOT}/shared/resolve-config.sh" ]; then
  source "${CLAUDE_PLUGIN_ROOT}/shared/resolve-config.sh"
elif [ -f "$HOME/.claude/shared/resolve-config.sh" ]; then
  source "$HOME/.claude/shared/resolve-config.sh"
else
  echo "ERROR: resolve-config.sh not found. Install via marketplace or run ./install.sh" >&2
  exit 1
fi
IFS='|' read -r REPO _TYPE <<< "$(resolve_artifact_typed requirements requirements)"
_BASE="$(dirname "$REPO")"

If the storage location type is git, sync before reading:

if [[ "$_TYPE" == "git" ]]; then
  cd "$_BASE" && git pull
fi

Extract requirements artifact path from storage configuration.

If not configured:

Requirements storage not configured

Configure in .claude/configuration.yml to rebuild index.
See: ~/.claude/templates/requirements-repo/README.md

Step 2: Confirm Rebuild

Use AskUserQuestion:

Rebuild requirements index?

Repository: ${repo_path}
Current index: ${index_status}

This will:
- Scan all requirement directories
- Extract metadata from each
- Rebuild index.json
- Validate integrity

Existing index will be backed up to:
  index.json.backup.${timestamp}

Time estimate: ~1 second per 100 requirements

Continue? [y/n]

Step 3: Backup Current Index

TIMESTAMP=$(date +%Y%m%d_%H%M%S)
cp ${repo_path}/index.json \
   ${repo_path}/index.json.backup.${TIMESTAMP}

✓ Backed up to: index.json.backup.${TIMESTAMP}

Step 4: Delegate to Archivist

Use Task tool with subagent_type: "archivist":

Task(archivist, "Rebuild requirements index

Repository: ${repo_path}

Process:
1. Scan all directories in repository root
2. For each directory with metadata.json:
   a. Read metadata.json
   b. Extract: id, title, description, tags, components, etc.
   c. Add to index tickets array
   d. Update tag/component/project frequencies
3. Skip directories: templates/, archive/, .git/
4. Handle missing or malformed metadata gracefully
5. Sort tickets by date (newest first)
6. Generate new index.json
7. Validate JSON structure
8. Write to repository
9. Report statistics and issues

Return:
- Tickets scanned
- Tickets added to index
- Issues found (missing metadata, malformed JSON, etc.)
- Tag and component counts
- Backup location
")

Step 5: Report Results

Success:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✓ Index Rebuilt Successfully
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Repository: ${repo_path}
Execution time: 2.3 seconds

SCAN RESULTS
────────────────────────────────────────────────
Directories scanned: 28
Requirements found: 25
Added to index: 24
Skipped: 1 (issues)

STATISTICS
────────────────────────────────────────────────
Unique tags: 45
Unique components: 78
Projects: 3
Date range: YYYY-MM-DD to YYYY-MM-DD

TAG FREQUENCIES (top 10)
────────────────────────────────────────────────
api              : 15
database         : 12
export           : 8
authentication   : 5
integration      : 4
...

COMPONENT FREQUENCIES (top 10)
────────────────────────────────────────────────
UserController   : 8
AuthService      : 5
ExportService    : 3
ApiController    : 3
...

ISSUES FOUND
────────────────────────────────────────────────
⚠ USER-100: Missing metadata.json (skipped)

Recommendation: Add metadata.json or move to archive/

BACKUP
────────────────────────────────────────────────
Old index backed up to:
  index.json.backup.20260203_143022

Index committed to git:
  commit abc123: "Rebuild requirements index"

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Test search: /search-requirements "export"

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

With Issues:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚠ Index Rebuilt with Issues
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Directories scanned: 30
Requirements found: 27
Added to index: 24
Skipped: 3 (issues)

ISSUES
────────────────────────────────────────────────
❌ USER-100: Missing metadata.json
   → Add metadata or move to archive/

❌ USER-101: Malformed metadata.json (invalid JSON)
   → Fix JSON syntax or regenerate metadata

⚠ USER-102: Missing required fields (title, description)
   → Update metadata.json with required fields

RECOMMENDATIONS
────────────────────────────────────────────────
1. Fix or archive problematic requirements:
   - USER-100: Add metadata.json
   - USER-101: Fix JSON syntax
   - USER-102: Add missing fields

2. Or move to archive/:
   mv USER-100 archive/2025/USER-100

3. Rebuild after fixing:
   /rebuild-requirements-index

Index is functional but incomplete.
Search will work but won't include skipped requirements.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Examples

Example 1: Simple Rebuild

/rebuild-requirements-index

Rebuilds index from all requirements in repository.

Example 2: After Manual Changes

# After manually editing metadata
/rebuild-requirements-index

Ensures index reflects manual changes.

Example 3: After Cleanup

# After moving old requirements to archive/
mv USER-* archive/2025/
/rebuild-requirements-index

Removes archived requirements from index.

When to Rebuild

Required

• Index corrupted - Invalid JSON, cannot parse
• Index missing - File deleted or never created
• Search fails - Errors when searching

Recommended

• After bulk operations - Archiving multiple requirements
• After manual edits - Direct changes to metadata.json
• After cleanup - Moving requirements to archive/
• Periodic maintenance - Monthly or quarterly

Optional

• After single archive - Automatic in /archive-requirements
• Normal usage - Index auto-updated on archive

Safety

Non-Destructive

• Original requirements files unchanged
• Old index backed up before rebuild
• Backup includes timestamp
• Can restore from backup if needed

Restore from Backup

If rebuild caused issues:

cd ${repo_path}

# Find backups
ls -lt index.json.backup.*

# Restore from backup
cp index.json.backup.20260203_143022 index.json

Then commit and push inline. Record a security-auditor confirmation for the restoration commit before pushing:

git add index.json
git commit -m "Restore index from backup"
bash "${CLAUDE_PLUGIN_ROOT}/hooks/record-audit.sh"
git push

Validation

The rebuild process validates:

Required fields:

• id (must be unique)
• title
• description
• status

Optional fields:

• tags (array)
• components (array)
• date (ISO format)
• project

Structure:

• Valid JSON syntax
• No duplicate ticket IDs
• All dates parseable
• Arrays are arrays (not strings)

Performance

Rebuild time:

• ~1 second per 100 requirements
• 25 requirements: ~0.25 seconds
• 500 requirements: ~5 seconds
• 1000 requirements: ~10 seconds

Scales well:

• Linear performance
• Low memory usage
• Can handle 1000+ requirements

Troubleshooting

Permission Denied

❌ Cannot write to repository

Path: /path/to/requirements-repo/index.json
Error: Permission denied

Check:
1. File permissions: chmod 644 index.json
2. Directory permissions: chmod 755 /path/to/requirements-repo
3. Git permissions

Fix and retry: /rebuild-requirements-index

Git Conflicts

❌ Git conflict when committing index

Another developer may have rebuilt simultaneously.

To resolve:
1. cd ${repo_path}
2. git pull --rebase
3. Retry: /rebuild-requirements-index

Invalid Metadata

⚠ Found 3 requirements with invalid metadata

Details:
- USER-100: Missing metadata.json
- USER-101: Invalid JSON syntax
- USER-102: Missing required field: title

Options:
1. Fix metadata in these requirements
2. Move to archive/: mv USER-100 archive/2025/
3. Skip and rebuild anyway (index will be incomplete)

How to proceed? [fix/archive/skip]

Maintenance Schedule

Recommended:

• After bulk operations - Immediately
• After manual changes - Immediately
• Routine maintenance - Monthly
• Before important searches - If index seems stale

Signs index needs rebuild:

• Search returns unexpected results
• Missing recent requirements
• Duplicate results
• Search errors

Advanced Usage

Rebuild with Custom Path

If multiple requirements repositories:

# Configure alternate repository temporarily
# Then rebuild
/rebuild-requirements-index

Rebuild After Migration

After migrating from old structure:

# Migrate old requirements to new format
# Then rebuild index
/rebuild-requirements-index

Scheduled Rebuilds

For periodic rebuilds, invoke the skill manually or set up a script that calls the rebuild logic from resolve-config.sh.

See Also

• /search-requirements <query> - Search using the index
• /archive-requirements [id] - Archive (auto-updates index)
• /load-requirements <id> - Load specific requirement