agentsclimarketplace

Plan & spec

10,724 rows, by stacks then stars

2,010 of these skill files have been read, by 1,360 distinct authors, and what they tell an agent counted. What Plan & spec authors agree on, and what they forbid

  • Brainstorming

    SWEStash/swe-workflow-skills/plugins/strategy/skills/brainstorming Skill

    1★ repo

    Facilitate divergent ideation before committing to a spec — Socratic questioning, widening the option space, challenging assumptions and inherited constraints, then converging on candidates. Triggers: brainstorm, let's explore ideas, what are our options, help me think through, generate ideas, what could we build, not sure what I want, explore approaches, ideate. Once ideas converge, hand off to prd-writing (WHAT/WHY) or feature-planning (breakdown) — this skill opens options; those close them.

  • Feature planning

    SWEStash/swe-workflow-skills/plugins/strategy/skills/feature-planning Skill

    1★ repo

    Break features into well-scoped tasks with acceptance criteria, risk assessment, and dependency mapping. Triggers: plan this, break this down, scope this feature, create tasks for, sprint planning, how should I implement this feature, user stories, acceptance criteria, dependency mapping, feature breakdown. Creates the plan — executing an already-approved plan checkpoint by checkpoint → plan-execution.

  • Project proposal

    SWEStash/swe-workflow-skills/plugins/strategy/skills/project-proposal Skill

    1★ repo

    Write lightweight project proposals for budget approval and go/no-go decisions — problem, business case, scope, rough estimates, risks, success criteria. Triggers: project proposal, project brief, business case, budget estimate, should we build this, go/no-go, risk assessment, cost-benefit, ROI, justify this project, stakeholder approval.

  • Project review

    SWEStash/swe-workflow-skills/plugins/strategy/skills/project-review Skill

    1★ repo

    Review a built project's execution health before a milestone — scope alignment, roadmap / execution-plan adherence, implementation maturity (what's production-ready vs stub/deferred), and the evidence it actually works (tests, coverage, validation results, changelog). Use strategic-review for vision/positioning/market; technical-debt-review for a pure code-health audit.

  • Strategic review

    SWEStash/swe-workflow-skills/plugins/strategy/skills/strategic-review Skill

    1★ repo

    Review a project's strategic position before going public, launching, or raising — vision, mission, value proposition, scope positioning, the defensible wedge, and a live competitive / market comparative analysis. Use project-review for execution/roadmap/implementation health; delegates deep market scans to deep-research.

  • Brainstorming

    SWEStash/swe-workflow-skills/skills/brainstorming Skill

    1★ repo

    Facilitate divergent ideation before committing to a spec — Socratic questioning, widening the option space, challenging assumptions and inherited constraints, then converging on candidates. Triggers: brainstorm, let's explore ideas, what are our options, help me think through, generate ideas, what could we build, not sure what I want, explore approaches, ideate. Once ideas converge, hand off to prd-writing (WHAT/WHY) or feature-planning (breakdown) — this skill opens options; those close them.

  • Configuration strategy

    SWEStash/swe-workflow-skills/skills/configuration-strategy Skill

    1★ repo

    A comprehensive SWE workflow, encoded. Might be useful to you too.

  • Effort estimation

    SWEStash/swe-workflow-skills/skills/effort-estimation Skill

    1★ repo

    Estimate engineering effort with agile techniques — story points, t-shirt sizing, three-point estimation, capacity planning.

  • Feature planning

    SWEStash/swe-workflow-skills/skills/feature-planning Skill

    1★ repo

    Break features into well-scoped tasks with acceptance criteria, risk assessment, and dependency mapping. Triggers: plan this, break this down, scope this feature, create tasks for, sprint planning, how should I implement this feature, user stories, acceptance criteria, dependency mapping, feature breakdown. Creates the plan — executing an already-approved plan checkpoint by checkpoint → plan-execution.

  • Plan execution

    SWEStash/swe-workflow-skills/skills/plan-execution Skill

    1★ repo

    Execute an already-approved plan with discipline — batch tasks into verifiable checkpoints, verify each with fresh evidence before marking it done, log drift, and stop to re-plan when reality diverges from the plan's assumptions. Triggers: execute the plan, implement the approved plan, work through this plan, continue/resume the plan, next phase, checkpoint. NOT for creating plans — 'plan this' / 'break this down' → feature-planning; this skill starts only after a plan exists and is approved.

  • Prd writing

    SWEStash/swe-workflow-skills/skills/prd-writing Skill

    1★ repo

    Write lightweight agile PRDs and technical RFCs that align stakeholders before implementation. Triggers: PRD, product requirements, RFC, request for comments, technical design doc, design document, tech spec, write requirements, what are we building, spec this out. Produces the WHAT and WHY — feature-planning handles HOW.

  • Project proposal

    SWEStash/swe-workflow-skills/skills/project-proposal Skill

    1★ repo

    Write lightweight project proposals for budget approval and go/no-go decisions — problem, business case, scope, rough estimates, risks, success criteria. Triggers: project proposal, project brief, business case, budget estimate, should we build this, go/no-go, risk assessment, cost-benefit, ROI, justify this project, stakeholder approval.

  • Project review

    SWEStash/swe-workflow-skills/skills/project-review Skill

    1★ repo

    Review a built project's execution health before a milestone — scope alignment, roadmap / execution-plan adherence, implementation maturity (what's production-ready vs stub/deferred), and the evidence it actually works (tests, coverage, validation results, changelog). Use strategic-review for vision/positioning/market; technical-debt-review for a pure code-health audit.

  • Rollback strategy

    SWEStash/swe-workflow-skills/skills/rollback-strategy Skill

    1★ repo

    Design safe rollback plans before deploying — identify irreversible changes, classify rollback complexity, create tested undo procedures. Triggers: rollback plan, rollback strategy, how do I undo this, can we revert, what if the deploy fails, safe to deploy, feature flag rollout, blue-green, database migration rollback, irreversible change.

  • Strategic review

    SWEStash/swe-workflow-skills/skills/strategic-review Skill

    1★ repo

    Review a project's strategic position before going public, launching, or raising — vision, mission, value proposition, scope positioning, the defensible wedge, and a live competitive / market comparative analysis. Use project-review for execution/roadmap/implementation health; delegates deep market scans to deep-research.

  • Technical debt review

    SWEStash/swe-workflow-skills/skills/technical-debt-review Skill

    1★ repo

    Strategic codebase health assessment — identify hotspots, categorize debt, produce remediation roadmap.

  • Test data strategy

    SWEStash/swe-workflow-skills/skills/test-data-strategy Skill

    1★ repo

    Design and generate test data — factories, synthetic data, property-based testing, boundary analysis, contract testing, load scenarios, GDPR-safe data. Triggers: test data, synthetic data, fake data, factory, seed data, fixtures, property-based testing, fuzz testing, boundary values, contract testing, Pact, load test data, anonymize, GDPR test data.

  • Planning

    kjhk3082/master-assistant-skill/skills/planning Skill

    1★ repo

    [EN] You MUST use this after brainstorming or when you have a clear design/spec but before writing any code. Breaks down work into actionable, verifiable steps. [KO] 브레인스토밍 후 또는 명확한 설계/사양이 있지만 코드를 작성하기 전에 반드시 사용해야 합니다. 작업을 실행 가능하고 검증 가능한 단계로 나눕니다.

  • Ollygarden otel collector config decomposition

    ollygarden/skills/skills/ollygarden-otel-collector-config-decomposition Skill

    1★ repo

    Decide and execute plain-file decomposition for OpenTelemetry Collector YAML. Use for "should I split this collector config?", "break up this otelcol YAML", "organize it by signal or team", or "create environment overlays". Leaves simple configs intact and proves warranted splits equivalent after merge. Not for Helm, Kustomize, or Terraform packaging; use otel-collector for component facts and ollygarden-otel-collector-config-validation for behavioral proof.

  • Ollygarden otel instrumentation planning

    ollygarden/skills/skills/ollygarden-otel-instrumentation-planning Skill

    1★ repo

    Plan Minimal Viable Instrumentation for a codebase. Use when starting instrumentation from scratch, assessing what to instrument in an existing application, or deciding what boundaries need manual vs auto instrumentation. Identifies application boundaries, classifies them as auto-instrumented or manual, selects signals, plans attributes with cardinality awareness, and produces an actionable instrumentation plan tied to SLOs/SLIs. Triggers on "what should I instrument", "add observability", "instrumentation plan", "MVI", or when scanning a codebase without existing instrumentation.

  • Rfc writer

    morzecrew/agent-skills/skills/rfc-writer Skill

    1★ repo

    Skills that make AI coding agents prove their work — reproduce before fixing, run before claiming, enforce what you build

    The same file is in 4 other repositories

  • Slice plan runner

    stevennitesh/programming-agent-skills/skills/.archive/slice-plan-runner Skill

    1★ repo

    Run a saved slice plan through multiple committed slices.

  • Slice plan

    stevennitesh/programming-agent-skills/skills/.archive/slice-plan Skill

    1★ repo

    Use when approved multi-step repo work truly needs a written execution plan or handoff with task boundaries, checks, execution mode, ownership scope, continuity, and final verification; skip tiny edits, one behavior, one bug, or issue-only/PR-only tracking.

  • To slice plan

    stevennitesh/programming-agent-skills/skills/.archive/to-slice-plan Skill

    1★ repo

    Create no-babysitting implementation slice plans.

  • To spec

    stevennitesh/programming-agent-skills/skills/custom/to-spec Skill

    1★ repo

    Synthesize settled source into a source-traced parent spec and publish it to the configured tracker.

  • Event exhibition

    simonkoehler/event-skills/event-exhibition Skill

    1★ repo

    For B2B participants: plan YOUR participation at others' B2B trade shows, expos, and sponsored conferences as an exhibitor or sponsor. B2B context only — not for consumer expos. Generates booth planning briefs, stand personnel training guides, lead capture strategies, sponsorship evaluation scorecards, pre-show marketing plans, and post-event ROI reports. Use this skill whenever someone asks to plan a trade show booth, prepare for a trade show, train booth staff, evaluate a sponsorship package, decide which events to sponsor, create a booth briefing, set up lead capture, plan pre-event outreach to target accounts, submit a CFP proposal for an external conference, or analyze ROI from event sponsorship. Also triggers for exhibit design briefs, stand personnel shift plans, giveaway planning, and post-show lead follow-up sequences. Part of the event-management-skills collection — covers the participant perspective while other skills cover the organizer perspective.

  • Event logistics

    simonkoehler/event-skills/event-logistics Skill

    1★ repo

    Manage venue selection, vendor coordination, and on-site operations for B2B events. Generates venue evaluation scorecards, vendor RFP templates, vendor briefing documents, run-of-show documents, floor plan briefs, load-in schedules, and on-site operations guides. Use this skill whenever someone asks to evaluate a venue, compare venues, write a vendor RFP, create a vendor brief, build a run-of-show, plan event setup and teardown, coordinate catering, manage AV requirements, plan on-site registration flow, create a floor plan brief, write a load-in schedule, or coordinate event day operations. Also triggers for venue site visit checklists, vendor contract review, emergency procedures, and staff deployment plans. Part of the event-management-skills collection — handles physical execution while other skills handle planning, content, and finance.

  • Event orchestrator

    simonkoehler/event-skills/event-orchestrator Skill

    1★ repo

    Coordinate multi-skill workflows for complex B2B event projects. Analyzes the user's request, determines the optimal skill execution order, and manages context passing between skills. Use this skill when a user's request spans multiple event domains (e.g., "plan a full conference" requires planner + budget + speakers + content + logistics), when the user is unsure which skill to start with, or when outputs from one skill need to feed into another. Acts as the intelligent router and workflow manager for the event-management-skills collection.

  • Event planner

    simonkoehler/event-skills/event-planner Skill

    1★ repo

    Plan and organize B2B events end-to-end: conferences, trade shows, expos, product launches, sales kickoffs, developer conferences, industry summits, roadshows, team offsites, company retreats, and community meetups. Generates event briefs, master timelines with T-minus milestones, phase-based checklists, stakeholder RACI matrices, risk registers, and post-event action plans. Use this skill whenever someone asks to plan an event, create an event timeline or checklist, write an event brief, organize a conference or offsite, coordinate a summit or retreat, assess event risks, structure event workstreams, or asks how far in advance to plan. Creates comprehensive event plans that connect to specialized skills for budgets, logistics, speakers, and content. Also triggers for hybrid event format selection, virtual event strategy and timeline, event RACI, post-event follow-up, or GDPR compliance for events. Gateway skill for the event-management-skills collection.

  • Event registration

    simonkoehler/event-skills/event-registration Skill

    1★ repo

    Design and manage registration workflows for B2B events: registration form design, ticket tier structures, pricing strategies, attendee data management, check-in processes, and attendee communication flows. Generates registration page specs, ticket tier matrices, confirmation email sequences, attendee data schemas, badge designs, and check-in plans. Use this skill whenever someone asks to set up event registration, design a registration form, create ticket tiers, plan check-in, manage attendee data, design badges, process attendee CSV files, set up early-bird pricing, plan group registration, or handle waitlist management. Also triggers for GDPR- compliant registration, attendee segmentation, no-show management, and capacity planning. Part of the event-management-skills collection.

  • Event reviewer

    simonkoehler/event-skills/event-reviewer Skill

    1★ repo

    Review and validate outputs from other B2B event skills for cross-skill consistency, completeness, and quality. Checks that budget figures match timeline assumptions, sponsorship tiers align with venue capacity, email timing matches registration deadlines, and GDPR compliance is consistent across all outputs. Use this skill after generating outputs from multiple event skills to catch inconsistencies, before presenting a complete event plan to stakeholders, or when the user asks to review or validate their event planning outputs.

  • Event speakers

    simonkoehler/event-skills/event-speakers Skill

    1★ repo

    Manage the full speaker lifecycle for B2B events: Call for Papers creation, speaker outreach, proposal review criteria, agenda building, session scheduling, speaker coordination, and presentation logistics. Generates CFP documents, speaker coordination templates, review scorecards, multi-track agendas, speaker briefing documents, and session format guides. Use this skill whenever someone asks to create a Call for Papers, write a CFP, find or invite speakers, review talk proposals, build a conference agenda, schedule sessions across tracks, create speaker briefing documents, manage speaker logistics, design session formats, write speaker invitation emails, plan a panel discussion, or coordinate keynote speakers. Also triggers for talk selection criteria, speaker diversity planning, session time allocation, and workshop design. Part of the event-management-skills collection.

  • Brand strategy

    krlan/leverbrain/skills/brand-strategy Skill

    no license1★ repo

    Build a comprehensive brand strategy, positioning framework, and communication guidelines for startups and products.

  • Api spec writer

    GustavoGutierrez/engineering-skills/skills/api-spec-writer Skill

    1★ repo

    Design complete API contracts in OpenAPI 3.0/3.1 YAML with endpoints, schemas, security, pagination, error handling, and RFC 7807 problem details. Use when asking to design an API, create an OpenAPI spec, define API endpoints, write API contracts, or generate a Swagger specification.

  • Frontend spec writer

    GustavoGutierrez/engineering-skills/skills/frontend-spec-writer Skill

    1★ repo

    Design complete frontend specifications from product requirements: UX flows, component hierarchies, component contracts (props/events), state management, responsive breakpoints, accessibility rules, and API integration mapping. Use when asking to design a frontend spec, component architecture, UI specification, or view specification.

  • Prd writer

    GustavoGutierrez/engineering-skills/skills/prd-writer Skill

    1★ repo

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    The same file is in 1 other repository

  • Release planner

    GustavoGutierrez/engineering-skills/skills/release-planner Skill

    1★ repo

    Trigger: release planning, rollout strategy, release waves, phased rollout, migration sequencing, canary release, rollback planning, go no-go criteria. Design a complete release execution plan connecting technical deployment with operational coordination and stakeholder communication.

  • Spec architect

    GustavoGutierrez/engineering-skills/skills/spec-architect Skill

    1★ repo

    Design high-level functional and technical specifications by defining scope, modules, contracts, boundaries, responsibilities, architecture models, constraints, and verification criteria.

  • Spec writer

    GustavoGutierrez/engineering-skills/skills/spec-writer Skill

    1★ repo

    Write, rewrite, or normalize structured `*.spec.md` specification files for agent-driven development. Use this whenever the user asks for a spec, requirements, acceptance criteria, implementation-ready documentation, feature definition before coding, or wants an existing idea/codebase turned into an actionable spec, even if they do not explicitly say "spec".

    The same file is in 1 other repository

  • Story refiner

    GustavoGutierrez/engineering-skills/skills/story-refiner Skill

    1★ repo

    Refine user stories into sprint-ready backlog items using INVEST checks, gap analysis, Gherkin acceptance criteria, edge cases, dependencies, and structured refinement questions.

    The same file is in 1 other repository

  • Task breakdown

    GustavoGutierrez/engineering-skills/skills/task-breakdown Skill

    1★ repo

    Break complex features, epics, or specs into small executable tasks with logical sequencing, dependencies, ownership, acceptance signals, and parallelization guidance.

  • Technical planner

    GustavoGutierrez/engineering-skills/skills/technical-planner Skill

    1★ repo

    Plan technical execution for software systems by organizing phases, dependencies, sequencing, infrastructure foundations, MVP scope, coordination points, and incremental architecture delivery.

  • Ss branch strategy

    jsirish/workflow-skills/skills/ss-branch-strategy Skill

    no license1★ repo

    Establish consistent branch-naming and default-branch conventions across all module repos when executing a major framework or CMS version upgrade. Covers integer branch naming, default-branch promotion, previous-version preservation, and the fork-and-upstream workflow for third-party modules. Use when planning or executing a major version upgrade across a suite of repos.

  • Implementation plan

    sainzs/santiagosainz-skills/skills/core/implementation-plan Skill

    1★ repo

    Convert a plan, PRD, backlog item, or vague feature into ordered implementation work with acceptance criteria and verification. Use when the user asks to break down work, make an implementation plan, create tasks, plan execution, or use slice-plan.

  • Request refactor plan

    rmerk/crewai-headless-flow/.agents/skills/request-refactor-plan Skill

    1★ repo

    Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

    The same file is in 13 other repositories

  • To spec

    rmerk/crewai-headless-flow/.agents/skills/to-spec Skill

    1★ repo

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    The same file is in 11 other repositories

  • To tickets

    rmerk/crewai-headless-flow/.agents/skills/to-tickets Skill

    1★ repo

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

    The same file is in 5 other repositories

  • Jira ticket plan audit

    rmerk/crewai-headless-flow/vendor/agent-skills/skills/jira-ticket-plan-audit Skill

    1★ repo

    Audit a PR diff against a saved Jira implementation plan at .agents/jira-plans/{KEY}.md. Checks file coverage, test strategy, backend escalation scope, and scope creep. Use after jira-ticket-implement or when user says audit AS-12345 against plan.

  • Jira ticket plan

    rmerk/crewai-headless-flow/vendor/agent-skills/skills/jira-ticket-plan Skill

    1★ repo

    Fetch a Jira issue from a ticket link or key in context, resolve the expected git branch for the ticket, and produce a Vue/TDD-grounded implementation plan saved locally to .agents/jira-plans/ (personal, never committed). For bugs, follow systematic-debugging investigation before fix steps. Optional plan-and-ship handoff to jira-ticket-implement. Jira is read-only (no comments or status changes). Use when the user passes a Jira URL, mentions a ticket key (e.g. AS-12345), or asks to plan or review work from Jira.

  • Planning and task breakdown

    rmerk/crewai-headless-flow/vendor/agent-skills/skills/planning-and-task-breakdown Skill

    1★ repo

    Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

    The same file is in 9 other repositories

  • Spec driven development

    rmerk/crewai-headless-flow/vendor/agent-skills/skills/spec-driven-development Skill

    1★ repo

    Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

    The same file is in 5 other repositories

  • Arxiv space paper to brief

    frankxai/starlight-agent-skills/skills/cosmos/arxiv-space-paper-to-brief Skill

    1★ repo

    Turn an astrophysics/space-science arXiv paper into a structured brief tuned for space audiences — adds object/mission context, instruments, and observational caveats. Use when summarizing an astro-ph paper, a space-science result, or a mission's published findings.

  • Arxiv paper to brief

    frankxai/starlight-agent-skills/skills/research/arxiv-paper-to-brief Skill

    1★ repo

    Turn an arXiv (or any research) paper into a structured, citation-faithful brief — problem, method, results, limitations, and why it matters. Use when summarizing a paper, building a literature digest, or asked to 'explain this paper' / 'TL;DR this arxiv link'.

  • Freelancer brief

    buildwitharup/cortex/skills/freelancer-brief Skill

    1★ repo

    Use when the user needs to write a brief for an external freelancer, agency, or vendor. Also triggers on "brief a freelancer", "write a creative brief", "vendor brief", "brief an agency", "content brief for writer", "design brief", "web development brief", "brief external team", "contractor brief", "outsource task".

  • Marketing budget planning

    buildwitharup/cortex/skills/marketing-budget-planning Skill

    1★ repo

    Use when the user wants to plan, build, or present an annual or quarterly marketing budget. Also triggers on "marketing budget", "annual budget planning", "budget allocation", "how much to spend on marketing", "marketing spend by channel", "budget for board", "marketing ROI planning", "Q planning", "budget template".

  • Ears to ddd

    anarefin/ai-agent-skills/ears-to-ddd Skill

    no license1★ repo

    Converts ANY EARS (Easy Approach to Requirements Syntax) specification from a layered-architecture project into a new DDD/CQRS/Event-Sourcing EARS file using the bits.ddd command-side patterns. The skill is domain-agnostic: it reads whatever concrete EARS file it is given as-is and derives the aggregate, commands, events, source data, validation, and status lifecycle from that input. Guides the user through batched architectural decisions then generates the output file. Use when the user says "convert EARS to DDD", "generate DDD EARS from <file>", "/ears-to-ddd <file>", or "map this EARS spec to DDD architecture".

  • Fix dev reviews

    anarefin/ai-agent-skills/fix-dev-reviews Skill

    no license1★ repo

    Fourth-pass closer for an EARS specification file produced by /springboot-to-ears. Consumes the two developer-review sections a human filled in directly in the spec — `## Review by Developer (code)` (source-code pointers to rules — or whole entities/enums — missing from the spec) and `## Review by Developer (business requirements)` (business decisions needing a human answer). For each unchecked entry it investigates the referenced code, writes a reviewable report, and — only after the user approves — folds confident findings in as code-free EARS statements, adds any missing entity/enum-state as a new `### <Name>` block (with all properties) in Domain Entities / Domain Concepts, and turns ambiguous findings and all business-requirement entries into [NEEDS REVIEW] Open Questions, then checks the entry off and annotates where it landed (module/subsection, entity/concept block, or Open Question) plus the EARS line number. Each `## Module:` and content `### Subsection` in the input carries a `> **Source files:**` annotation (springboot-to-ears Rule 14) which this skill preserves, uses as a supplemental locate hint, and keeps accurate. Trigger when the user types `/fix-dev-reviews <path-to-EARS-file>` (controller path(s) may be passed as an optional override).

  • Grails fix dev reviews

    anarefin/ai-agent-skills/grails-fix-dev-reviews Skill

    no license1★ repo

    Fourth-pass closer for an EARS specification file produced by /grails-to-ears. Consumes the two developer-review sections a human filled in directly in the spec — `## Review by Developer (code)` (source-code pointers to rules — or whole entities/enums — missing from the spec) and `## Review by Developer (business requirements)` (business decisions needing a human answer). For each unchecked entry it investigates the referenced code, writes a reviewable report, and — only after the user approves — folds confident findings in as code-free EARS statements, adds any missing entity/enum-state as a new `### <Name>` block (with all properties) in Domain Entities / Domain Concepts, and turns ambiguous findings and all business-requirement entries into [NEEDS REVIEW] Open Questions, then checks the entry off and annotates where it landed (module/subsection, entity/concept block, or Open Question) plus the EARS line number. Each `## Module:` and content `### Subsection` in the input carries a `> **Source files:**` annotation (grails-to-ears Rule 14) which this skill preserves, uses as a supplemental locate hint, and keeps accurate. Trigger when the user types `/fix-dev-reviews <path-to-EARS-file>` (entry-point (controller / action service) path(s) may be passed as an optional override).

  • Grails to ears

    anarefin/ai-agent-skills/grails-to-ears Skill

    no license1★ repo

    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 — including single controllers, single action services, multiple controllers/action services, or an entire plugin directory — 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. 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).

  • Skill snapshot

    anarefin/ai-agent-skills/merge-ears-workspace/skill-snapshot Skill

    no license1★ repo

    Merge, combine, or consolidate two or more EARS (Easy Approach to Requirements Syntax) specification .md files into a single coherent EARS spec. Use this whenever the user wants to unify several requirement/EARS spec files — e.g. "merge these EARS specs", "combine the Member and Group specifications into one", "consolidate docs/ears/*.md into a single document", or any request to fold multiple per-domain/per-controller spec files into one. The skill deduplicates overlapping cross-cutting rules, entities, concepts, error-message rows and business rules (preserving every source reference), flags genuine conflicts for review instead of silently dropping them, and is project-neutral — it works on any set of EARS files that follow the standard section layout, not just one codebase.