Daniel Avila #262 Jan 9, 2026
  • feature-analyzer.md 25 lines · 798 B
feature-analyzer.md

Phase 1: Discovery

Goal: Understand what needs to be built

Initial request: $ARGUMENTS

Actions:

  1. Create todo list with all phases
  2. If feature unclear, ask user for:
    • What problem are they solving?
    • What should the feature do?
    • Any constraints or requirements?
  3. Summarize understanding and confirm with user

Phase 2: Run with Feature Analyzer Skill

Use the Skill tool to invoke the "feature-design-assistant" skill and follow its complete process.

Next step

More commands in orchestration, in alphabetical order.