Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Workflow for authoring requirements and specifications: drafting, review, validation, etc.
tags
["workflow"]
baseSchema
docs/schemas/workflow.md
<description_and_purpose>
Prevents premature drafting by enforcing HITL gates where every <req> unit receives explicit user approval before proceeding. Each phase produces traceable artifacts (Final Requirements Set, Validation Pack, Traceability Matrix). Input: user request for new requirements, edits, review, refactor, or validation; USE SKILL requirements-authoring and PROACTIVELY REQUIRE its use in all phases and subagents.
</description_and_purpose>
<workflow_phases>
<prerequisites phase="0", applies="ALL">
All Rosetta prep steps MUST be FULLY completed
USE SKILL load-project-context, hitl
MUST ALWAYS use todo tasks ledger, ASAP. Phases are sequential. Independent tasks can run in parallel.
No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping
Every phase MUST update requirements-authoring-flow-state.md in FEATURE TEMP with: phase name, status, artifact produced, and open questions.
Orchestrator and subagents MUST USE SKILL requirements-authoring.
If task is to reverse engineer orchestrator MUST USE SKILL reverse-engineering.
Keep requirement identifiers in code comments only, must not be user facing.
If /goal is set repeat phases 5-6 until goal is met, then continue with the rest of phases.
This workflow MUST be used with Fable, Opus, GPT-5.5+ class models => IF NOT - DEMAND USER TO SWITCH MODEL
IMPORTANT! If the task is to reverse engineer requirements, spawn MULTIPLE subagents with each handling one unit of analysis (one screen, one page, one controller, one endpoint, etc) to effectively prevent hallucinations by narrow scoping for phases intent_capture, outline, draft, validate.
Artifact: Discovery Summary (context, existing requirements, constraints, affected files).
Done when: scope boundaries and relevant requirement files are identified.
Identify requirement areas (FR, NFR, interfaces, data, traceability)
Record assumptions and unknowns
Required skills: requirements-authoring
Recommended skills: reverse-engineering
Artifact: Research Notes (sources, constraints, prior art, reusable requirement patterns).
Done when: relevant references are gathered OR no additional sources are needed.
Skip when: local context is complete and no external standards are needed.
Gather supporting docs and prior decisions
Collect requirement patterns and quality criteria
Capture measurable thresholds and terminology constraints
Artifact: Intent Capture.
Done when: intent is restated, scope and goals confirmed, assumptions listed, and questions resolved.
Restate intent and confirm scope and goals
List assumptions and targeted questions
HITL: present intent capture and get explicit approval
Resolve blockers before outlining or drafting
Required skills: requirements-authoring
</intent_capture>
Artifact: Requirement Outline (areas, file mapping, ID strategy, traceability plan).
Done when: user approves structure and requirement batching strategy.
Propose MECE structure and area abbreviations
Map files and IDs without writing final requirement text
HITL: get user approval on structure and scope
Required skills: requirements-authoring
Artifact: Draft Requirement Units (per the requirements-authoring skill's requirement-unit asset).
Done when: every in-scope requirement has schema-complete draft and explicit user decision.
Draft in small batches using <req> schema
Use EARS for FRs and measurable metrics for NFRs
Keep unresolved or deferred units as Draft
Modify files directly, do not show to user
Update <req> schema if older/missing fields
Required skills: requirements-authoring
If reverse engineering - it must be possible to rewrite using requirements only completely from scratch without old code present.
Artifact: Validation Report (rubric results, conflict checks, gap checks, risks).
Done when: checklist passes and unresolved issues are either fixed or explicitly deferred.
Run validation using the requirements-authoring skill's validation rubric
Run conflict checks and gap checks
Verify traceability source -> goal -> req -> test
HITL: review findings with user as a narrative / story /walk-through
Required skills: requirements-authoring
Recommended skills: reverse-engineering
If reverse engineering: MUST additionally validate there are NO hallucinations or made-up requirements
Review all drafts requirements with user by providing a clear and exact story as a narrative/walk-through of a functionality of the application that this affected, use simple words and sentences (consider human doesn't know internal implementation). If possible you can also do that from point of view of the actor that this requirements affect (user of the app, admin of the dashboard, etc)
You should combine affected and existing requirements for the proper narrative/story
If there are multiple stories - create todo task to review each story separately
Review story-by-story with user for approval, provide referenced content, examples, etc
The narrative must still be very specific so that it allows to fully approve every aspect of requirements
Do not assume user has a context, explain like user sees this first time
Must review all assumptions and quirks
</user_review>
Artifact: Final Requirements Set, Validation Pack, Traceability Matrix, Change Log.
Done when: artifacts are stored in target location and state file is complete.
Deliver final approved requirement set
Update index and links
Update the change log using the requirements-authoring skill's change-log asset
Mark state as complete
Required skills: requirements-authoring
Coding must be performed using coding-flow (ask, recommend, switch), on switch do not load requirements-use skill, as requirements-authoring is superior already.
