What problem does it solve? Feature work often goes undocumented, leaving teams without a record of what was built, which decisions were made, and why. This Skill generates structured task documentation in Markdown—both planning templates for new features and archive records extracted from completed work—so implementation knowledge persists across sessions. ## Core Features & Use Cases - Task Creation: Generates a planning template with context, acceptance criteria, implementation phases, technical decisions, and verification commands, saved as .agent/tasks/TASK-{XX}-{slug}.md. - Task Archiving: Analyzes the conversation to produce a completion record covering what was built, files modified, challenges and solutions, and testing results, with a user verification checkpoint before saving. - Index and Knowledge Graph Sync: Updates the Navigator index in .agent/DEVELOPMENT-README.md and syncs tasks to the knowledge graph so decisions become queryable memories. - Use Case: After finishing an OAuth integration, say "document this feature" to produce a complete archive with technical decisions, files modified, and verification results, then have it indexed and synced automatically. ## Quick Start Ask the assistant to create a task doc for your next feature or to document the feature you just completed.