anarefin·anarefin/ai-agent-skills/grails-to-ears/SKILL.md

grails-to-ears

Skill1 starsChanged 5 months agoNo licenceView on GitHub

Reverse engineer a Grails 2.5.x project into a 100% complete EARS (Easy Approach to Requirements Syntax) specification file. Use this skill when the user wants to extract business requirements from an existing Grails codebase — operating on exactly the controller(s) and/or action service(s) the user names (single or multiple, no sibling discovery, no directory expansion) — and produce a standalone, code-free .md EARS file that can serve as a source of truth for regenerating the system in any architecture (DDD, CQRS, Event Sourcing, etc.). The skill also auto-resolves its own Open Questions on the first pass (Step 6.5): a fresh read-only subagent chases each question's breadcrumb footer and folds confident answers back into the spec as finalised statements, leaving only genuinely unresolvable items as [NEEDS REVIEW] — so a separate /resolve-open-questions run is usually unnecessary. The data-model closure spans cross-module / other-plugin entities: every entity reached through the reference closure — including those owned by a different plugin or module — is opened and fully field-expanded (full transitive closure, no module-depth limit), and is never punted to an Open Question. Each module and content subsection is annotated with a `> **Source files:**` line listing the full project-relative paths it was extracted from, so a developer can cross-check the spec against the codebase (the EARS statements themselves stay code-free).