brief-writer

To convert a one-sentence intent into a structured work brief, the system analyzes the statement to extract subject, action, scope, and stakeholders. It then populates domain-specific templates with focused content and converts implicit requirements into measurable acceptance criteria.

The best way to generate project briefs from short intents is to use an automated expansion tool that loads domain-specific templates and translates implicit requirements into measurable acceptance criteria. This approach reduces ambiguity and rework by enforcing completeness validation before presenting the brief.

You can create GitHub issues from a one-line intent by configuring tracked workflows within your project setup. The system processes the intent into a structured brief and persists it directly as a GitHub issue instead of using local file storage.

Yes, structured brief generation works with custom workflow templates by loading domain-specific brief templates from your workflow.yaml file. If specific templates are not configured there, it falls back to loading template files from the templates directory.

To handle slug collisions during local saves, the system enforces unique kebab-case slugs using an atomic write protocol. This mechanism ensures file integrity and prevents data overwrites when multiple briefs are generated.

Your project needs YAML frontmatter metadata in generated work briefs to provide structured, machine-readable context for downstream design and implementation pipelines. This metadata enables consistent tracking and integration within automated project workflows.