author-brief

Convert unstructured stakeholder input into DoR-compliant product briefs.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/phanijapps/engram --skill author-brief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: author-brief
Source: https://github.com/phanijapps/engram/tree/main/.claude/skills/author-brief
Command: npx skills add https://github.com/phanijapps/engram --skill author-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the friction of converting raw, unstructured stakeholder input—such as emails, messages, or issue descriptions—into formal, actionable product briefs that meet Definition of Ready (DoR) standards.

Core Features & Use Cases

  • Structured Intake: Automatically extracts key product fields like Outcome, Appetite, and Rabbit holes from messy text.
  • Workflow Integration: Validates brief completeness and queues them directly into workspace.toml for team visibility.
  • Use Case: A stakeholder sends a vague email about a new feature request; use this skill to parse the email, elicit missing constraints, and generate a standardized draft brief in the project repository.

Quick Start

Invoke the author-brief skill by providing the raw text from your email or issue and asking the agent to turn it into a product brief.

Frequently Asked Questions about author-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert unstructured stakeholder emails into product briefs?

To convert unstructured stakeholder emails into product briefs, provide the raw text to the agent so it can extract key project metadata like Outcome and Appetite, generating a standardized draft. This parses messy input into actionable documentation.

What is a Definition of Ready compliant product brief?

A Definition of Ready (DoR) compliant product brief is a standardized document containing validated project metadata such as Outcomes, Appetite, and Rabbit holes. It ensures workflow continuity by meeting completeness standards before development begins.

How do I extract product metadata from messy text inputs?

You extract product metadata from messy text by passing the unstructured input to the skill, which automatically identifies and structures fields like Outcome and Rabbit holes. This generates a standardized product brief ready for team visibility.

Can I queue draft product briefs directly into workspace configuration files?

Yes, you can queue draft product briefs directly into workspace configuration files. The skill validates brief completeness and integrates with workspace.toml to queue drafts for further development, ensuring team workflow visibility.

Does this product brief intake process work with issue descriptions?

Yes, the product brief intake process works with issue descriptions. It parses raw issue text, elicits missing constraints, and generates a standardized DoR-compliant draft brief within your project documentation directory.