Skip to content

Management Workflow

End-to-end flow for turning an idea into department-ready specs.

Doc chain (execution order)

idea  →  prd  →  srs  →  user-story  →  roadmap
                          ↓
                       tasks  →  acceptance  →  deps
                          ↓
                  (handoff to backend / frontend / design / qa)

Each step depends on the previous one. The prerequisite gate blocks a step if its upstream doc is missing or still draft. See Prerequisite Gate.

One-time setup (after cloning nepwalk-management)

  1. Confirm ../nepwalk-docs/ exists as a sibling directory.
  2. Open the repo in any agent (Claude Code, Codex, OpenCode, Gemini, Cursor).
  3. The agent reads AGENTS.md automatically. No tool-specific setup needed.

Per-session bootstrap

The agent runs this automatically:

  1. Read PROJECT_STATE.md — current state, blocked items, active version.
  2. Read dept.yaml — inputs, outputs, agents, tools.
  3. Load .ai_flow/skills/caveman_skill.md and management_skill.md.
  4. Report session start.

Typical first run

idea: trip management for Nepal tour operators
  → interview → idea_v1.md (status: draft)

idea: promote v1
  → status: review

prd: focus on offline mode and version log
  → interview → PRD_v1.md (draft)

srs: nestjs + postgres + prisma
  → interview → SRS_v1.md (draft)

user-story:
roadmap:
tasks: backend auth phase
acceptance: backend
deps:

management: publish docs/management/mvp/v1/PRD_v1.md
  → PR to nepwalk-docs

Versioning

All docs go to ../nepwalk-docs/docs/management/mvp/v<N>/. Minor versions stay in the same major folder. See Versioning.

When something feels wrong

Read Prerequisite Gate first. If a doc upstream is missing or stale, fix that before the current step. Do not work around the gate.