feature-discuss

Structure feature discovery and planning into reviewable documents and ADRs.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/AbsolutSystems/absolutpowers --skill feature-discuss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-discuss
Source: https://github.com/AbsolutSystems/absolutpowers/tree/main/claude/skills/feature-discuss
Command: npx skills add https://github.com/AbsolutSystems/absolutpowers --skill feature-discuss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a vague feature idea, stakeholder request, or gap report into a clear, reviewable product plan. It keeps the conversation focused on intent, scope, user needs, and architecture before any implementation starts.

Core Features & Use Cases

  • Feature discovery: Clarifies what the user actually wants, what problem it solves, and what success looks like.
  • Architecture-aware planning: Analyzes the existing codebase and recommends practical technical approaches instead of guessing.
  • Epic handling: Breaks large initiatives into phased plans, with a main roadmap and per-phase planning docs.
  • Review-ready output: Produces planning documents, edge cases, implementation notes, and architecture decision records when needed.
  • Use case: A product owner wants to add push notifications, and this Skill helps refine the request, assess the codebase, split the work into phases if needed, and draft the plan.

Quick Start

Ask me to discuss a new feature or a gap in existing functionality, and I will help clarify the goal, analyze the codebase, and draft the appropriate planning document.

Frequently Asked Questions about feature-discuss

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

FAQPage Schema
How do I turn a vague feature idea into a reviewable product plan?

Epic decomposition breaks large initiatives into a main roadmap and per-phase planning documents. You initiate planning for a large feature, and the Skill splits the work into phased plans with architecture recommendations for each phase.

Can I get architecture recommendations based on my existing codebase?

The Skill produces planning documents, edge cases, implementation notes, and architecture decision records. These ADR-ready decision records capture technical choices with review-gated outputs to ensure stakeholder alignment before development.

What is the best way to decompose a large epic into phased plans?

Epic decomposition breaks large initiatives into a main roadmap and per-phase planning documents. You provide a large feature request, and the Skill splits the work into phased plans with architecture recommendations for each phase.

Does this feature planning workflow support problem-report handoffs?

Problem-report handoffs are supported directly within the feature discovery process. You submit a gap report or problem description, and the Skill structures the discussion to clarify user needs and draft the appropriate planning document.

When do I need an architecture decision record for feature planning?

Architecture decision records are needed when feature planning requires capturing specific technical approaches for stakeholder review. The Skill generates ADR-ready decision records alongside planning documents to ensure architecture choices are documented before implementation.