hirogakatageri/new-requirement

New Requirement — Add Work to the Guild

Create a new requirement stub and a task for the product-owner to gather full details.

Arguments

Parse from $ARGUMENTS or user input:

| Argument | Description | |----------|-------------| | title | Short title for the requirement (e.g., "User Authentication") | | description | Brief description of what's needed |

Steps

1. Check for Guild

Read .guild/BOARD.md.

If not found:

No guild found. Run /guild:check-in to initialize first.

Stop here.

1.5. Offer to Clear the Board

If the board has any existing requirements, tasks, or plans (check BOARD.md tables and the .guild/requirements/, .guild/tasks/, .guild/plans/ directories), ask the user:

The guild board currently has {N} requirements, {N} tasks, and {N} plans.
Clear the board before adding this new requirement? (yes / no)

If "yes": Invoke the guild:clear-board skill (it will handle confirmation and deletion), then proceed.

If "no": Proceed without changes.

If the board is empty, skip this step.

2. Gather Details

If title is not provided, ask the user:

What's the title of this requirement? (e.g., "User Authentication", "Payment Integration")

If description is not provided, ask the user:

Briefly describe what you need. The product-owner will gather full details later.

3. Read Board Counters

Read BOARD.md frontmatter to get:

• next-req → use as REQ ID
• next-task → use as TASK ID

Zero-pad IDs to 3 digits (e.g., 1 → 001).

4. Create Requirement Stub

Write .guild/requirements/REQ-NNN.md:

---
id: REQ-NNN
title: "{title}"
status: draft
created: {today's date}
---

# {title}

## Summary

{description}

## User Stories

_To be gathered by the product-owner._

## Technical Considerations

_To be determined._

## Out of Scope

_To be determined._

5. Create Product-Owner Task

Write .guild/tasks/TASK-NNN.md:

---
id: TASK-NNN
title: "Gather requirements for {title}"
agent: product-owner
status: pending
requirement: REQ-NNN
plan: null
depends-on: []
priority: high
created: {today's date}
---

## Objective

Interview the user and gather comprehensive requirements for: {title}

{description}

## Context

- Requirement: .guild/requirements/REQ-NNN.md

## Acceptance Criteria

- [ ] Requirement document fully written with user stories
- [ ] Acceptance criteria defined for each story
- [ ] Edge cases identified
- [ ] Technical considerations documented
- [ ] Out of scope clearly defined

## Work Log

## Follow-up Tasks

- Plan {title} implementation | agent: architect | priority: high

6. Update BOARD.md

Using the Edit tool, make these updates:

1. Increment counters in frontmatter:

   • next-req → increment by 1
   • next-task → increment by 1

2. Add task to Backlog — append a row:

   | TASK-NNN | Gather requirements for {title} | product-owner | REQ-NNN | high | {today's date} |
   

3. Add requirement to Requirements — append a row:

   | REQ-NNN | {title} | draft | 0/1 done |
   

7. Confirm

Requirement created!

  Requirement: REQ-NNN — {title}
  Task: TASK-NNN — Gather requirements for {title} (product-owner)
  Status: Added to backlog

The product-owner will gather full details during the next work cycle.
Run /guild:check-in to start working.

Rules

• Never overwrite existing files — if REQ-NNN.md already exists, something went wrong with counters
• Always increment counters — prevent ID collisions
• Keep the stub minimal — the product-owner will flesh it out
• Pre-populate Follow-up Tasks — the standard chain starts with an architect task