feature-management

Manages feature folder lifecycle, delta-specs, and feature-scoped output routing in .giantmem/features/.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/bearded-giant/claude-code-config --skill feature-management-bearded-giant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-management
Source: https://github.com/bearded-giant/claude-code-config/tree/main/skills/feature-management
Command: npx skills add https://github.com/bearded-giant/claude-code-config --skill feature-management-bearded-giant

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about feature-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage features that span multiple Claude Code sessions?

Create a feature folder with /new-feature, which scaffolds proposal.md, tasks.md, and delta-specs under .giantmem/features/{name}/. Status persists in features.json, so resuming a session restores the active feature's plans, notes, and scoped output routing.

What is the difference between proposal.md and delta-specs?

proposal.md captures intent, scope, and approach but not behavior. Delta-specs in specs/{domain}/spec.md define behavior contracts with ADDED, MODIFIED, and REMOVED Requirements using Given/When/Then scenarios, and merge into the source-of-truth spec on /complete-feature.

When should I use /abandon-feature instead of /complete-feature?

Use /abandon-feature when the feature was framed but never built, since it archives without merging delta-specs. /complete-feature merges delta-specs into the source-of-truth spec, which would falsely claim behavior that does not exist.

How does feature-scoped output routing work?

When a feature has status in_progress, session output that would normally go to top-level .giantmem/ subdirectories is redirected inside the feature folder. Plans, research, reviews, and filebox items land under .giantmem/features/{name}/ instead.

Does the feature notes file capture commands automatically?

Yes, while a feature is in_progress the model appends reusable commands, identifiers, and config discoveries to {name}-notes.md silently in the background. Secrets like tokens and passwords are redacted with placeholders before appending.