Decompose multi-feature product briefs into testable feature specifications.
npx skills add https://github.com/phanijapps/engram --skill receive-brief-phanijapps
Please help me install this Agent Skill. Skill: receive-brief Source: https://github.com/phanijapps/engram/tree/main/.claude/skills/receive-brief Command: npx skills add https://github.com/phanijapps/engram --skill receive-brief-phanijapps
This skill solves the friction of receiving unstructured, multi-feature product briefs by systematically decomposing them into independently shippable, testable feature specs.
Invoke the receive-brief skill to process the attached product brief and decompose it into individual shippable specs.
High-intent search queries and answers about installing and using this skill.
To decompose a PRD into shippable specs, this skill breaks down unstructured product briefs into granular, independently testable feature slices based on shippability criteria. It elicits missing load-bearing fields and scaffolds the necessary spec files for development intake.
Automated traceability for product briefs is a mechanism that maintains a live, auto-rolled-up spec map tracking delivery status. It establishes bidirectional traceability between brief-level outcomes and spec-level acceptance criteria without requiring manual maintenance.
To break down a 30-page product requirements packet, invoke this skill to cut the work into feature-sized slices. It processes the attached product brief, elicits missing requirements, and scaffolds spec and plan files for each shippable feature.
Automated coverage linting works with bidirectional spec traceability by validating that every brief-level outcome maps directly to spec-level acceptance criteria. This ensures the decomposed feature specifications remain independently testable throughout the intake workflow.
Yes, you can split complex product briefs by shippability rather than arbitrary architectural layers. The intelligent decomposition evaluates requirements and cuts the work into granular, independently shippable slices tailored for engineering delivery.
A limitation of automated PRD decomposition is that it requires structured product briefs to elicit missing load-bearing fields effectively. If the initial requirements packet lacks clear outcomes, the generated spec slices may need manual refinement before sprint planning.
Reading-Advantage-ThailandGenerate and validate PRD drafts using the Gemini CLI.
farmountainPrioritize product backlog items and generate sprint plans from capacity data.
prof-danielcValidate code implementations against specification requirements and acceptance criteria.
tgmarinhoConvert conversation content into a Product Requirements Document and publish it to an issue tracker.
