Codex-project-manifest

What problem does it solve? Projects accumulate files and conversation history across sessions without a structured record of what exists, why decisions were made, or how artifacts relate to each other. This Skill produces annotated bibliography-style manifests that document files, threads, and dependencies with unique IDs so projects remain navigable and handoff-ready. ## Core Features & Use Cases - Annotated File Inventory: Track every file with a unique ID, type, summary, and rationale-focused notes explaining why design decisions were made. - Conversation Thread Tracking: Log sessions with accomplishments, decisions, files created or modified, and next steps. - Relationship Mapping: Record typed relations (depends_on, implements, supersedes, documents) between entities with annotations. - Use Case: When onboarding a collaborator to an existing project, generate a manifest.yaml from the directory, annotate key files with context, and export a Markdown report so the newcomer understands structure and history without reading every file. ## Quick Start Ask the agent to create a project manifest for the current directory, assigning IDs to each file and summarizing the conversation threads that produced them.