improve-issue

Turning a vague GitHub issue into an implementation-ready spec requires ingesting the issue and linked dependencies to produce structured requirements. It expands vague requests into concrete, testable acceptance criteria covering edge cases and error paths.

Writing acceptance criteria for Phoenix LiveView issues involves expanding requests into observable behaviors aligned with project conventions. It enforces rules like gettext for user-visible strings, soft-delete practices, and event audit fields.

Yes, this issue enrichment approach works with the Ash framework by producing implementation-grade specifications tailored to Ash and Phoenix codebases. It ensures generated specs match project-specific rules before development starts.

To update an existing enriched-spec block without duplicating it, the system detects current drafts and replaces them idempotently. It outputs a marker-wrapped spec block that preserves or updates the original content reliably.

You need to ingest linked issues for requirements clarification when a parent issue depends on context from other tasks. Ingesting these linked issues ensures the final specification captures all necessary dependencies and implementation details.