What problem does it solve? Long-running features that span multiple sessions lose context: plans scatter across directories, specs drift from implemented behavior, and reusable commands discovered mid-session get forgotten. This Skill provides a persistent feature folder system under .giantmem/features/ with lifecycle tracking, spec management, and scoped output routing. ## Core Features & Use Cases - Feature lifecycle commands: Scaffold, start, pause, complete, abandon, and reopen features via slash commands like /new-feature and /complete-feature, with status tracked in features.json and _index.md. - Three-spec model: Separates intent (proposal.md), behavior deltas (specs/{domain}/spec.md with ADDED/MODIFIED/REMOVED Requirements), and the accumulated source-of-truth spec merged on completion. - Living notes and todo sync: Silently appends reusable commands and identifiers to a per-feature notes file, and parks user-actionable follow-ups in a repo-qualified doit list via the doit MCP. - Use Case: You start a multi-session OAuth feature. Run /new-feature oauth-ttl, work across several days while research, reviews, and notes auto-route into features/oauth-ttl/, then run /complete-feature to merge the delta-specs into the repo's source-of-truth spec. ## Quick Start Ask the assistant to create a new feature named oauth-ttl so it scaffolds the feature folder and begins routing session output into it.