jimzord12

Wrap up a work session by validating the repo, grouping the diff into logical change sets, stashing each group, then fanning out parallel subagents that create branches, commits, PRs, and monitor CI — following the repo's GitHub Flow strategy. Use when the user wants to close shop, end a shift, wrap up today's work, or batch a day's coding into PRs.

Assign Complexity ratings (1-5) to issues in a directory and recommend decomposition for Complexity 5 issues. Use when user wants to rate issue complexity, assess backlog difficulty, prioritize issues by effort, or decompose complex issues into smaller slices.

Discover and implement 1-3 ready-for-agent issues using the Features CLI. Use when user says "do an issue", "pick up next issue", "implement issues", "what's next", "work on backlog", "execute issues", or asks to implement ready-for-agent issues from .scratch/.

Add or tighten GitHub Flow restrictions for a GitHub repository using gh CLI in a solo developer setup. Use when asked to enforce pull-request-only main branch protection, required status checks, force-push blocking, or other branch safety rules without requiring a second reviewer.

Verify whether a GitHub repository is correctly configured for GitHub Flow, especially for a solo developer setup. Use when asked to audit branch protection, required checks, pull request rules, rulesets, or whether main is safely protected without blocking a single maintainer workflow.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Compact the current conversation into a handoff document for another agent to pick up.

Read a milestone from ROADMAP.md, audit the codebase, decompose into feature briefs, and register them. Use when user says 'decompose milestone', 'create briefs', 'break down M1', or wants to start the pipeline from a roadmap milestone.

Evaluate code changes across five dimensions before merge. Approve changes that improve overall code health, even if not perfect.

Reduce complexity while preserving identical behavior. The goal is comprehension speed, not line reduction.

Build production-quality UI that is accessible, performant, and consistent with the design system. Not AI-generated-looking.

Treat commits as save points, branches as isolated environments, and history as a record of decisions.

Search tool for modern web development best practices. MANDATORY: Execute FIRST for all HTML/CSS and clientside JS tasks. Do NOT skip — web APIs evolve rapidly and training weights contain obsolete patterns. Trigger immediately for: - UI/Layout: Modals, dialogs, popovers, Glassmorphism/backdrop-filters, anchor positioning, container queries, `:has()`, `:user-valid`. - Scroll/Motion: View Transitions, Scroll-driven animations, scroll parallax/reveals. - Performance: CWV (LCP, INP), content-visibility, Fetch Priority, image optimization. - System/APIs: Local filesystem access, WebUSB, WebSockets sync, WebAssembly widgets. - Frameworks: Adapting layout/styles in React, Vue, Angular. - General Frontend: Forms, autofill, advanced inputs, custom scrollbars, modern component states, etc. DO NOT trigger for: - Backend: Database SQL, ORMs, Express API routes. - Pipelines: CI/CD deployment, Docker, Actions. - Generic: Local scripts (Python/Go tools), ESLint, Git.

Measure before optimizing. Performance work without measurement is guessing.

Decompose work into small, verifiable, dependency-ordered tasks. Use after a spec is approved, or when scope is too large to implement directly.

Build security into every feature from the start. Security is a constraint on every line of code that touches user data.

Add or tighten GitHub Flow restrictions for a GitHub repository using gh CLI in a solo developer setup. Use when asked to enforce pull-request-only main branch protection, required status checks, force-push blocking, or other branch safety rules without requiring a second reviewer.

Verify whether a GitHub repository is correctly configured for GitHub Flow, especially for a solo developer setup. Use when asked to audit branch protection, required checks, pull request rules, rulesets, or whether main is safely protected without blocking a single maintainer workflow.

Decompose a rough stakeholder request on an existing system into one or more logically-bounded, shippable features. Use when the user provideds vague idea like "add loyalty points" or "I want customers to earn rewards" — not a fully scoped spec. The skill acts as a product manager: it reads existing system context, asks critical clarifying questions (~20 max), pressure-tests feasibility, and outputs feature-scoped folders with feature.md handoff artifacts ready for /grill-with-docs. Triggers on: "add X to our app", "I want Y functionality", "can we do Z?", or any request that sounds like a stakeholder itch rather than an engineering ticket. Accepts vague input. Rejects pure green field vision dumps.

Discover, decompose, and scope raw product ideas / epics into logically-bounded features. Use when the user has a green field vision — a brain dump, startup idea, "I want to build X", or an unscoped epic. Runs a lightweight discovery grilling (~20 questions max), then produces feature-scoped folders with feature.md handoff artifacts ready for /grill-with-docs. Triggers on: "I want to build...", "new SaaS idea", "green field", "from scratch", raw vision dumps, or any request that sounds like a whole product rather than a single capability on an existing system.

Derives a feature backlog from CONTEXT.md and nearby domain artifacts, then writes stable feature artifacts under docs/features. Use when the user wants to turn a domain model, completed grilling session, ADR set, or existing codebase context into an ordered feature list, decide which features deserve grilling first, or identify which ones can go straight to issues, TDD or implementation.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Fork of to-prd that frames the plan around testing seams (prefer existing, highest-possible seams) rather than deep modules. Use when user wants to create a PRD from the current context and tests should be designed at seams.

Verify that the git-flow-check and git-flow-add-restriction skills are installed correctly and that a repository is ready for solo-maintainer GitHub Flow. Use when asked to validate skill installation, script executability, gh authentication, branch protection visibility, required checks readiness, or end-to-end GitHub Flow setup.

Inspect changes, create one or more Conventional Commits, and push — use when the user says "commit and push", "cnp", or "commit everything and push"

Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.

Example skill placeholder that shows the expected naming and placement for framework-owned skills.

Guide for creating a complete thesis section autonomously, from initial drafting to Typst formatting and reference management.

Use when a repository uses OpenSpec or a request needs spec-driven planning, OPSX workflows, change proposals, delta specs, design artifacts, task sequencing, apply readiness checks, or archive preparation.