bartoszarendt
UserLoop engineering for AI coding agents — shaping the whole run, not one prompt: a Markdown-first overlay of task records, role boundaries, verification evidence, and review gates that holds across multi-hour work
Categories
Indexed Skills (17)
blocked-state
Use when an agent or the loop hits a wall it cannot clear on its own – provider outage, rate limit, missing credentials, an impossible or contradictory task, review deadlock, merge conflict, no implementation artifact produced, or an exhausted attempt budget / self-loop with no progress – and must record a durable, resumable pause. Defines needs_context, blocked markers, task-file status updates, block categories, and how the task resumes.
change-request-gate
Use when a task is classified `type: change-request` because it changes a locked architecture, process, plan, or repository decision. Defines the docs-first approval gate that must pass before implementation and how files-backed or GitHub-backed task records are held blocked until then.
debugging-before-fixes
Use the moment a required check, test, build, or runtime behavior fails or surprises – before proposing or applying any fix, including on every needs_revision iteration that involves a defect. Defines feedback-loop-first debugging, root-cause phases, calibrated hypotheses, tagged debug instrumentation, confirmed root-cause reporting, and the stop rule after 3 failed fix attempts.
decision-capture
Use when recording, updating, accepting, or superseding a durable project decision that constrains future work, including a maintainer's promotion of an already-recorded policy-level verification observation. Covers tracked Markdown decision records under .agenticloop/decisions/, maintainer ownership, proposed vs accepted state, source-linked discoverability, supersession, and decision.recorded events.
event-logging
Use when a role needs to emit an Agentic Loop workflow-gate event (role.invoked, task.created, task.started, check.run, review.started, review.result, decision.recorded, blocked, needs_context, task.closed, summary.published) and must resolve the event logging command, write concise event entries, or confirm that event logging is disabled or unavailable. Owns the command-resolution recipe, the disabled/non-blocking rules, and the event data conventions.
frontend-design-quality
Use when implementing or revising any frontend UI – landing pages, marketing sites, portfolios, app screens, dashboards, or components – and when choosing layout, typography, color, spacing, motion, or styling. Enforces a design-read first, real design systems, anti-slop discipline, accessibility, and a pre-flight visual audit so the interface does not look templated or AI-generated.
github-attribution
Use whenever an agent authors or reads a GitHub issue, pull request, or comment body, or writes an agent-authored commit message. Covers the [[agent: <name>]] body trailer, Task:/Agent: commit trailer, and how to read cooperative attribution when multiple roles share one GitHub identity.
loop-retrospective
Parked, human-invoked skill. Use when a human explicitly asks for a retrospective that turns repeated agent-process friction into durable improvements. Converts repeated blocked categories, check failures, review iterations, or recurring follow-up topics drawn from event logs into skill updates, docs entries, or follow-up task records. Not part of the closeout gate.
parallel-delegation
Use when an authorized multi-task work unit needs its required current Parallel Opportunity Scan, especially when 2 or more ready independent tasks may parallelize, or the orchestrator must decide serial versus parallel execution, or when planning, reviewing, joining, troubleshooting, or boundedly reconciling parallel lanes, leases, structured write ownership, classified managed joins, distinct shared exports or package scripts, backend-specific writes, knowledge coupling, cross-lane finding disposition, semantic conflict between lane artifacts, verification topology, integration rehearsal, or the human merge checkpoint.
review-and-accept
Use when the maintainer reviews an implementation artifact against its task record and decides accepted vs needs_revision, and when the engineer responds to review feedback. Defines GitHub review markers, files-backed `review_status`, ordered three-lens review, evidence rules, disputed-items protocol, and mandatory triage before acceptance.
role-delegation
Use when the orchestrator starts or resumes a task loop, routes first-run project-map confirmation, creates a task record handoff, hands off implementation, routes review, or runs closeout. Ensures real host delegation happens when available, or an explicit bounded single-agent role assumption is used when it is not, while files-backed and GitHub-backed delegation rules plus human checkpoints are followed.
setup-agenticloop
Use when a maintainer or human is setting up Agentic Loop in a target project for the first time, when source document names are non-standard or ambiguous, when .agenticloop/project.md is still unconfirmed, or when a human wants to update its development-stage profile. Discovers bounded candidate project docs once, gathers bounded backend and lifecycle evidence, proposes document selections and task conventions, asks for confirmation, and writes confirmed project-map values plus setup confirmation state.
task-closeout
Use when preparing pre-certification closeout once covered tasks are accepted, running the final closeout gate once the resulting candidate is integrated or frozen and certified, finishing a human-identified work unit in a flat project, or cleaning up an accepted worktree after integration. Defines conditional source-plan synchronization, what final closeout inspects, the durable status marker it posts, the work-unit certification gate, and the human approval gate for grouped projects. Final closeout is a verify-and-mark gate; it does not write a separate summary file.
task-record-contract
Use when creating, updating, or reading the task record for a single implementation task. Covers required task sections, no-placeholder rules, files-first task-file frontmatter, work-unit summary template, implementation artifact linkage, and safe GitHub projection posting practices. Backend projections are documented in agenticloop/backends/.
tdd-implementation
Use when implementing any code change for a task – new behavior, a bugfix, or a revision after review – before writing the production code. Defines the failing-test-first cycle, public-seam testing, vertical slices, scaffold and infra handling, and counters to common excuses for tests-after-code.
verification-evidence
Use before claiming any work state – done, fixed, passing, green, complete, mergeable – and whenever a required or cited check times out, is unexpectedly expensive, or needs a retry. Defines the identify-run-read-verify gate, timeout evidence and retry records, and the baseline/lane-final/integrated/post-merge verification topology with evidence-identity and reuse rules.
work-unit-audit
Use when every task in a work unit is accepted and the whole unit must be certified by the auditor before closeout, when routing a non-certifying audit report into remediation tasks, or when a re-audit is required because remediation changed the audited artifact. Defines the audit packet, the six audit perspectives, findings, verdicts, the separate audit budget, and the closeout certification gate.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.