workflow-idea

Create a PRD and a functional specification tracking table together. The PRD captures "why and what", the tracking table captures "what to build and how far along". This is a Layer 2 skill (optional harness).

Prerequisites

#	Check	On failure
1	.wiki symlink exists	"Run /wiki-init first"

Workflow

1. Understand the feature

Read the user's description. Then ask 3-5 critical clarifying questions via AskUserQuestion. Each question must have lettered options (A, B, C).

Focus only on essential gaps:

• Problem/goal clarity
• Core functionality scope
• Boundaries (what's NOT included)
• Success criteria
• Target user specificity

The user responds with short answers like "1A, 2C, 3B".

2. Determine save location

1. Read .wiki/CONTRIBUTING.md to understand the wiki structure
2. Suggest locations for both files via AskUserQuestion
3. Let the user confirm or choose different paths

3. Generate PRD

Numbering: PRD-YYYYMMDD-{seq} where {seq} is 01, 02, etc.

PRD Template

# PRD-{id}: {Feature Name}

Created: {date}
Status: Draft
Tracking: [SPEC-{product-name}.md](path-to-spec)

## Introduction
{What is this feature and why does it matter? One paragraph.}

## Goals
{What are we trying to achieve? Bullet list.}

## Target User
{Who specifically needs this? Role, context, pain point.}

## User Stories
{As a [role], I want [capability] so that [benefit].}

## Non-Goals (Out of Scope)
- {What this feature explicitly does NOT do}

## Design Considerations
{UI/UX notes, if applicable}

## Technical Considerations
{Constraints, dependencies, tech stack notes}

## Success Metrics
- {How do we know this worked? Measurable.}

## Open Questions
- {Unresolved decisions}

Note: Functional Requirements are NOT in the PRD. They live in the tracking table (SPEC file) to avoid duplication.

4. Generate tracking table

From the PRD's goals and user stories, extract concrete features and organize them by domain into a tracking table.

Tracking Template

# Functional Specification: {Product Name}

Source: PRD-{id}
Updated: {date}
Work Items: [projects/{project}/work-items/](../projects/{project}/work-items/)

## {Domain Name}

| ID | Feature | Status | Work Items |
|----|---------|--------|------------|
| {PREFIX}-001 | {feature} | pending | |
| {PREFIX}-002 | {feature} | pending | |

ID format: Domain prefix (3 letters) + sequential number. Examples: USR-001, PAY-001, NTF-001

Status values: pending, partial, done, deferred

Work Items column: Left empty at creation. Filled by /workflow-next-plan when work-item files are created and linked.

5. Add to Wiki Focus

Edit AGENTS.md to add both files to ### Wiki Focus.

6. Next steps

Tell the user:

• PRD and spec saved paths
• "Use /workflow-next-plan to check coverage and pick the next task"
• "Both documents are living documents — edit anytime"