claudeconfigurator: Instructions file for Codex

Agent Instructions

Project Management with Mycelium

This project uses Mycelium (myc) for task and epic management.

Quick Reference

# Initialize mycelium in this project (creates .mycelium/ directory)
myc init

# Create an epic (a large body of work)
myc epic create --title "Feature X" --description "Build feature X"

# Create tasks within an epic
myc task create --title "Implement Y" --description "Build the implementation for Y" --epic 1 --priority high --due 2025-12-31

# Task priorities: low, medium, high, critical
# Task status: open, closed

# List tasks
myc task list
myc task list --epic 1
myc task list --overdue
myc task list --blocked

# Manage dependencies (task 1 blocks task 2)
myc task link blocks --task 1 2
myc deps show 2

# Close tasks (blocked tasks cannot be closed without --force)
myc task close 1

# Assign tasks
myc assignee create --name "Alice" --github "alice"
myc task assign 1 1

# Link to external resources
myc task link github-issue --task 1 "owner/repo#123"
myc task link github-pr --task 1 "owner/repo#456"
myc task link url --task 1 "https://example.com"

# Project overview
myc summary

# Export data
myc export json
myc export csv

Data Model

• Epic: A large body of work with a title and optional description (e.g., a feature or milestone)
• Task: A unit of work with a title and optional description, optionally linked to an epic
• Dependency: Task A blocks Task B (B cannot close until A is closed)
• Assignee: Person assigned to a task (can have GitHub username)
• External Ref: Link to GitHub issues/PRs or URLs

Git Tracking

The .mycelium/ directory contains the SQLite database and should be committed to git:

git add .mycelium/
git commit -m "Add mycelium project tracking"

Follow-ups (myc followup, alias myc fu)

Lightweight scratch table for non-blocking "oh-by-the-way" items captured mid-work — bugs, questions, ideas, things the user should look at later. Separate from tasks (no epic/priority/deps/assignee). Most follow-ups are resolved by the user, not the agent.