manage-features

Split, add, deprecate, and re-prioritize project features with audit documentation.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/0xobat/claude-skills --skill manage-features
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-features
Source: https://github.com/0xobat/claude-skills/tree/main/dev/skills/manage-features
Command: npx skills add https://github.com/0xobat/claude-skills --skill manage-features

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured protocol for managing changes to a project's feature list mid-development, ensuring clarity and maintainability.

Core Features & Use Cases

  • Feature Splitting: Break down large features into manageable, single-session tasks.
  • Adding/Deprecating: Seamlessly incorporate new requirements or retire obsolete features while maintaining an audit trail.
  • Re-prioritization: Adjust the order of feature implementation based on dependencies or blockers.
  • Auditing: Regularly check the feature list for consistency, completeness, and granularity.
  • Use Case: During a coding session, you realize a feature like "Implement user authentication" is too broad. Use this skill to split it into "Basic login", "Session management", and "OAuth integration", documenting each change.

Quick Start

Use the manage-features skill to split the feature 'F012' into smaller, atomic pieces.

Frequently Asked Questions about manage-features

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

FAQPage Schema
How do I split a large project feature into smaller development tasks?

Feature splitting breaks down large requirements into manageable, single-session tasks. You can deconstruct a broad feature like user authentication into atomic pieces such as basic login, session management, and OAuth integration, documenting each change to maintain an accurate feature list.

What is the best way to manage adding and deprecating features mid-development?

Managing feature evolution involves seamlessly incorporating new requirements or retiring obsolete features while maintaining a detailed audit trail. This ensures your feature list remains accurate and maintainable throughout the entire development lifecycle without losing historical context.

How do I re-prioritize features based on development dependencies?

Re-prioritization adjusts the order of feature implementation based on dependencies or blockers. You can dynamically shift feature priorities within your project list to resolve development bottlenecks and ensure accurate progression tracking.

Can I audit a project feature list for consistency and completeness?

Auditing regularly checks your feature list for consistency, completeness, and granularity. This process ensures your project requirements remain accurately documented and maintainable, verifying that each feature is scoped correctly for development.

When should I re-prioritize features in an agile development workflow?

You should re-prioritize features in an agile development workflow when dependencies or blockers emerge that impact the current task order. Adjusting the implementation sequence ensures development continues efficiently without being stalled by structural feature list constraints.