anarefin
- 18 skills
- 0 followers
- 5 hours ago last updated
- ▌ Merge Ears 2 · anarefin bundleMerge, 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.
- ▌ Graphify · anarefin bundleany input (code, docs, papers, images, videos) to knowledge graph. Use when user asks any question about a codebase, documents, or project content - especially if graphify-out/ exists, treat the question as a /graphify query.
- ▌ Merge Ears · anarefin bundleBuild a catalog (index / inventory / manifest) of every Grails action or Spring Boot endpoint found across one or more EARS (Easy Approach to Requirements Syntax) specification .md files, with the source-code reference, module/domain, and originating EARS file for each. Use this whenever the user wants to list, catalog, index, inventory, or tabulate the actions/endpoints described by their EARS specs — e.g. "catalog the actions in these EARS files", "build an action/endpoint index from docs/ears/", "list every endpoint across these specs with its source file", "make a manifest of all controller actions in my EARS specs", or any request to enumerate the entry points of a set of EARS specifications into a single table. Accepts individual EARS files (paths or globs) OR a directory of EARS files — no pre-merging required. Works on any EARS files that follow the standard reverse-engineered layout, Grails or Spring Boot, not just one codebase.
- ▌ Code Review · anarefinReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
- ▌ Ears To Ddd · anarefin bundleConverts 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".
- ▌
- ▌
- ▌ Book Summarizer · anarefinUse this skill whenever a user uploads a PDF book (technical or otherwise) and wants a beginner-friendly summary, study guide, or chapter breakdown. Triggers on phrases like: "summarize this book", "explain this book for beginners", "extract key takeaways", "make this book easier to understand", "chapter summary", "study guide for this book", "break down each chapter", "simplify this book", "explain the concepts in this book". Also trigger when a user uploads a PDF and asks anything like "help me understand this" or "what is this book about" — even if they don't explicitly say "summarize". Produces a polished single-file HTML document with a chapter nav sidebar, dark/light mode toggle, and a standardized beginner-friendly layout for every chapter.
- ▌ Fix Dev Reviews · anarefinFourth-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:**`
- ▌ Implement Queue · anarefin bundleImplement an entire folder of tickets in dependency order, each in a fresh subagent context, with preflight, per-ticket external verification, one commit per ticket, retry-once, and a circuit breaker — running to completion without pausing. Use this whenever the user wants a whole ticket queue or backlog folder worked through in one go: "implement all the tickets in tickets/", "run the queue", "work through the backlog", "burn down tickets/", "start the implementation queue", or when they ask to triage or resume a queue run that halted. Do NOT use this for implementing a single named ticket or for open-ended feature work.
- ▌ Implement Ticket · anarefinImplement ONE ticket end to end — TDD, typechecking, a green suite, review, and a single commit. Use when the user points at exactly one ticket, issue, or slice to build: "implement this ticket", "implement issue 42", "implement 03-reserve-stock.md", "build the reserve-stock slice". Do NOT use for a folder or set of tickets worked through in sequence — that is implement-tickets. Do NOT use for open-ended work with no ticket behind it.
- ▌ Implement Tickets · anarefinImplement a set of tickets one after another, each in its own fresh subagent context, reviewing each one as it lands, working the dependency frontier, and stopping at the first ticket that cannot be completed. Use when the user asks to work through multiple tickets in order — "implement the tickets", "work the frontier", "run through .scratch/<feature>/issues", "do tickets 01 through 05". Pairs with /to-tickets, which produces the tickets, and sequences the implement-ticket skill, which does the work. Do NOT use this for a single ticket — that is implement-ticket, singular.
- ▌ Article Summarizer · anarefinDeep-read any article, blog post, or web page and produce a structured expert analysis: concise summary, key bullet points, reader action items, and domain-adaptive expert commentary. Use this skill whenever the user shares a URL (Medium, Substack, dev.to, HN, any blog) or pastes article/post content and asks to "summarize", "analyse", "break down", "review", "read this", "what do you think of this", "give me the key points", "TL;DR this", or similar. Also trigger when the user drops a raw URL without any instruction — assume they want the full analysis. Works for any domain: engineering, product, finance, science, design, business, etc.
- ▌ Review Spring Boot · anarefin bundlePerforms a full enterprise production-readiness review of Spring Boot projects (single- or multi-module) across architecture, Spring/JDK practices, performance, memory, concurrency, data, API, security, resilience, caching, messaging, observability, testing, ops, cloud, quality, and scalability. Auto-detects Spring Boot and JDK versions from the project, lets the user pick which review areas to run, and writes a timestamped report to the project root. Use when the user asks to review a Spring Boot project or backend, requests a production-readiness or enterprise-readiness assessment, or invokes /review-spring-boot.
- ▌
- ▌ Grails Fix Dev Reviews · anarefinFourth-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:**` anno
- ▌ Resolve Open Questions · anarefinSecond-pass automation for an EARS specification file produced by /springboot-to-ears. Walks every `[NEEDS REVIEW]` item in the spec's `## Open Questions` section, executes the breadcrumb commands from the item's `*Hint for reviewer:*` footer, and either resolves the question (rewriting the entry and citing the resolution on every affected EARS statement) or leaves it open untouched. Trigger when the user types `/resolve-open-questions <path-to-EARS-file>`.
- ▌ Article Summarizer 2mins · anarefinFast 2-minute read of any article, blog post, or web page: a tight summary, the most critical key points, and 1–2 sharp actions — all strictly from the content, delivered instantly with no back-and-forth. Use this skill when the user wants a rapid digest and says things like "quick summary", "TL;DR", "2 min version", "give me the gist", "what's the takeaway", "brief breakdown", or drops a URL and wants fast signal. Also triggers when the user just shares a URL or article text with no instruction and speed or brevity is implied. Works for any domain.