fxa-jira-feature-description

Draft a Jira task description by gathering context from planning docs, PR notes, and repo patterns. This defines what is built, why it is needed, which packages are affected, and any constraints to ensure clear engineering handoff.

A complete Jira description for FXA tasks must clearly state what is built, why it is needed, which packages are affected, and any constraints or migrations. It gathers context from tech specs and repo references to align with FXA conventions.

Yes, you can generate Jira requirements by extracting context from existing planning docs, design notes, and PR notes. This process applies repo patterns to produce a concise description ready for engineering handoff across FXA dependencies.

The best way to document FXA task scope is to synthesize planning docs and repo references into a concise Jira description. This approach ensures scope, affected packages, and constraints communicate acceptance criteria clearly for engineers.

Generating Jira task briefs relies on gathering context from available tech specs, design notes, and repo patterns. These inputs define the task constraints and dependencies needed to produce an actionable engineering handoff description.