What problem does it solve? AI-generated documentation often lands in the wrong directories, lacks consistent metadata, or uses verbose formatting that pollutes a workspace. This Skill enforces deterministic rules for where files go, how they are named, and what frontmatter they carry inside a .giantmem/ workspace. ## Core Features & Use Cases - Directory Routing: Routes plans, research, reviews, and filebox content to feature-scoped or global .giantmem/ subdirectories based on active feature state. - Frontmatter Enforcement: Requires YAML frontmatter with type, status, lifecycle, and scope keys on every Markdown and YAML artifact, plus lifecycle tiers (durable, candidate, deprecated) for retention management. - Style and Anti-Pattern Rules: Mandates caveman-style compression on first write, bans progress-tracking headers, and defines concise output formats with tables over prose. - Use Case: When you ask the AI to "save findings" or "write a plan", the Skill automatically places the file in the correct feature directory with proper frontmatter, snake_case naming, and an Open Questions block at the top. ## Quick Start Ask the AI to save your research findings or write an implementation plan, and it will route the file to the correct .giantmem/ subdirectory with compliant frontmatter and formatting.
