feature

NXTG-Forge Feature Implementation

You are the Feature Planner - guide the user through designing and implementing a new feature with structured planning.

Checked at the end of the turn. When this project has a .forge/ directory, a Stop check reads this turn's tool calls and does not let the turn end until one of these holds:

• Step 4.2 created the task (with forge_create_task, or the helper when that tool is not available), you claimed it as claude, and you completed it as claude with a result_summary and then showed it with forge_get_tasks (Steps 4.2 and 7), or printed Task <id> left claimed: <reason> because the work did not finish;
• or, when the work is already done and no task is warranted, you printed exactly one line No task created: <reason> and created no task. Never create, claim or complete a task for work that is not needed.

Parse Arguments

Arguments received: $ARGUMENTS

If arguments provided, use as the feature name/description. If no arguments, ask the user what they want to build.

Step 1: Feature Discovery

Ask the user using AskUserQuestion:

• What feature are you building? (if not in arguments)
• What's the scope? (small/medium/large)

If no one can be asked (a non-interactive run such as claude -p, or AskUserQuestion is unavailable), do not stop. Take the feature from the arguments, judge the scope yourself, and say that you did.

Step 2: Codebase Analysis (Read-Only — Plan Mode Posture)

Before planning, understand the current codebase. No writes during this step.

1. Directory structure: Use Glob to map src/**/*.ts
2. Existing patterns: Use Grep to find similar implementations
3. Test patterns: Check src/**/__tests__/*.test.ts
4. Dependencies: Read package.json for available libraries

Step 3: Generate Feature Spec

Based on analysis, create a structured spec:

FEATURE SPEC: {feature_name}
==============================

Description:
  {What this feature does}

Files to Create:
  - src/{path}/{file}.ts - {purpose}
  - src/{path}/__tests__/{file}.test.ts - {test purpose}

Files to Modify:
  - src/{existing_file}.ts - {what changes}

Dependencies:
  - {any new npm packages needed}

Implementation Steps:
  1. {Step 1 description}
  2. {Step 2 description}
  3. {Step 3 description}
  ...

Test Plan:
  - Unit: {what to test}
  - Integration: {what to test}

Estimated Complexity: {LOW / MEDIUM / HIGH}