lead

To write specs and PBIs for a dev agent, provide a detailed feature brief to generate concrete deliverables, scope definitions, and Linear issues with proper dependencies. This ensures the autonomous agent can execute tasks independently.

Decomposing feature planning into atomic PBIs involves creating precise specs that map directly to concrete deliverables, establishing clear Definition of Done and parent relationships for backlog governance. This enables independent task execution.

Creating Linear Epics and PBI issues with dependencies requires inputting a detailed feature brief, which outputs structured issues with required fields, parent relationships, and scope definitions to govern your backlog.

Yes, you need a detailed feature brief to generate specs for autonomous task execution. The brief provides the necessary context to output precise specs, atomic PBIs, and Linear issues that a dev agent can independently implement.

Generated specs for backlog planning are saved to the specs/{feature-domain}/spec.md directory path. This structure ensures the dev agent can access the precise implementation details and atomic PBIs during execution.

You should not use automated specs for backlog grooming when lacking a detailed feature brief, as generating atomic PBIs and Linear issues requires concrete input to establish proper dependencies and clear Definition of Done.