Feature Requirements: issue-94

Feature Requirements: issue-94

Metadata

• Feature: issue-94
• Status: REVIEW
• Created: 2026-02-02
• Author: ZERG Plan Mode
• Source: https://github.com/rocklambros/zerg/issues/94

1. Problem Statement

1.1 Background

The /zerg:plan command captures requirements through multi-phase interactive discovery. After user approval, the command ends abruptly with no guidance on next steps, no documentation task in the plan output, and existing documentation across GitHub/wiki has gaps in command/flag coverage.

1.2 Problem

Three related gaps:

1. No post-approval handoff — users must manually know to run /z:design
2. Documentation updates are never part of generated plans — docs drift from code
3. Command/flag documentation is incomplete across surfaces (docs/commands.md, wiki zerg-*.md pages)

1.3 Impact

• Users lose momentum after plan approval (no next-step guidance)
• Documentation falls behind with every feature shipped
• Users discover undocumented flags through trial and error

2. Users

2.1 Primary Users

ZERG users running /zerg:plan to start feature development

2.2 User Stories

• As a user, I want to be prompted with next steps after plan approval so I don't lose momentum
• As a user, I want every plan to include a documentation task so docs stay in sync
• As a user, I want all command flags documented so I can discover capabilities without reading source

3. Functional Requirements

3.1 Workstream A: Post-Approval Prompt

3.2 Workstream B: Documentation Task in Requirements Template

3.3 Workstream C: Command/Flag Documentation Audit

4. Non-Functional Requirements

4.1 Consistency

• Wiki command pages use zerg-*.md naming convention
• Flag tables use consistent format across all documentation surfaces
• No contradictions between docs/commands.md, wiki pages, and command source files

4.2 Backward Compatibility

• No breaking changes to plan command behavior for users who don't interact with the prompt
• "Stop here" option preserves existing behavior exactly

5. Scope

5.1 In Scope

• Modify plan.md and plan.core.md — add post-approval AskUserQuestion
• Modify plan.details.md — add Documentation section to requirements template
• Audit and fix docs/commands.md
• Audit and fix wiki zerg-*.md command pages
• Audit zerg-Reference.md, README.md, CLAUDE.md for flag coverage

5.2 Out of Scope

• Auto-invoking /z:design (user will be instructed manually)
• Changing non-command wiki pages (e.g., Getting-Started.md, FAQ.md)
• Adding new commands or flags
• Modifying the plan command's discovery phases (1-4)

5.3 Assumptions

• plan.md and plan.core.md are kept in sync (same content)
• Wiki is editable via git clone of rocklambros/zerg.wiki.git
• All 26 commands have corresponding wiki pages

6. Dependencies

6.1 Internal Dependencies

7. Acceptance Criteria

7.1 Definition of Done

• Post-approval AskUserQuestion prompt works with all 3 options
• "Clear context" option instructs user to /compact then /z:design
• "Stop here" option completes normally (same as current behavior)
• TaskUpdate fires correctly regardless of user choice
• Requirements template includes Documentation section referencing /zerg:document
• Documentation section specifies zerg-*.md naming for command wiki pages
• All 26 commands audited against docs/commands.md — gaps fixed
• All 26 commands audited against wiki pages — gaps fixed
• Cross-cutting capability flags documented in appropriate locations
• /z:* shorthand aliases documented

7.2 Test Scenarios

8. Open Questions

9. Documentation

Execute /zerg:document after implementation to update all documentation surfaces based on changes made. Ensure:

• All ZERG commands and flags are accounted for
• Wiki command pages follow the zerg-*.md naming convention (non-command pages unaffected)
• Before executing, plan via /zerg:design and estimate via /zerg:estimate