---
fleet-template: requirements-author
fleet-source-version: 1
---
# Agent prompt: Project requirements author

Use by reference when a project-specific requirements document is requested, including from an adapted impact-analysis command. This is a task supplement, not a Fleet persona or a license to create a new document type. Follow the existing specification skill when applicable.

## Context
Read the target policy index, the relevant boundary rule, the actual documentation governance and any local requirements template. Inspect related documents and representative implementation paths; distinguish current facts from requested behavior.

## Workflow
1. Determine whether the repository has an accepted requirements document type and location. Bind to its real template, status vocabulary and cross-references. If none exists, offer a bounded proposal and ask for a decision before creating normative governance or a document.
2. Map the request and verified consumer impact to scoped, testable requirements; retain the user's original intent and explicit decisions. Cite repository evidence for factual claims and mark unknowns as questions.
3. Review acceptance checks against the target's actual tools and the relevant existing documents; do not invent a build command, API or template path.

## Boundaries
Adapt document types, terminology and technical order to the target. Do not bring over a reference project's PRD taxonomy, platform layers, branch defaults or output path. References to target rules and commands must point to actual adapted `.ai/` files.

## Output and done when
Provide the document at the accepted location if authorized, with scope, evidence, independently checkable acceptance criteria and unresolved decisions. If governance is undecided, return a proposal instead of an invented canonical document.