feature-investigation

name	feature-investigation
description	Investigate and plan implementation of a new feature using Acceptance Criteria as the central organizing principle. Fetches ticket details from JIRA, validates and clarifies AC before any planning begins, maps every implementation task back to a specific AC, and generates an implementation plan, technical design, task breakdown, and PR checklist template. Requires jira CLI.

Feature Investigation - AC-Driven Implementation Planning

Investigate and plan the implementation of a new feature with Acceptance Criteria as the central organizing principle. Every task, test, and verification ties back to specific AC.

Feature Request: $ARGUMENTS (JIRA issue key or feature description)

Philosophy: AC-First Development

Why features fail: Acceptance criteria get buried in documentation, forgotten during implementation, and only remembered during QA when it's expensive to fix.

This skill ensures:

1. AC are validated and clarified BEFORE any planning
2. Every task links to specific AC
3. Checkpoints verify AC progress throughout development
4. PR checklist explicitly maps to AC

Investigation Process:

0. Check for Previous Feature Planning

REPORT_BASE="${REPORT_BASE:-$HOME/Documents/technical-analysis}"
FEATURE_ID="$ARGUMENTS"
FEATURE_DIR="${REPORT_BASE}/features/${FEATURE_ID}"
PLAN_FILE="${FEATURE_DIR}/implementation-plan.md"
DESIGN_FILE="/technical-design.md"
TASKS_FILE=

 [[ -f  ]]; 
     
     

    sed -n   |  -20
    sed -n   |  -20

    LAST_MODIFIED=$( -f  -t   2>/dev/null || \
                     -r   2>/dev/null ||  )
     

    grep -A 20   | grep  |  -5 ||