jrgilbertson
- 13 skills
- 0 followers
- 10 hours ago last updated
- ▌ Route Work · jrgilbertson bundleUse only when the user explicitly asks to route a work kickoff to its first workflow owner or decide whether a proven in-flight owner should continue.
- ▌ Repo Gardener · jrgilbertson bundleUse when running or interpreting a scheduled or manual repository-gardening pass for one repository, including first-use setup of `.agents/repo-gardener.yaml` and its gardening tracker. Do not use for merging, releasing, deploying, creating follow-up issues, contacting customers, or performing an already-selected implementation outside a gardening run.
- ▌ Storm Research · jrgilbertson bundleUse only for requests whose deliverable is a full research briefing, a STORM-style investigation, or an evidence review across multiple independent perspectives. The work compares competing evidence, maps contradictions and blind spots, and supports decisions, investments, negotiations, long-form writing, presentations, or learning a new domain.
- ▌ Managing Issues · jrgilbertson bundleUse when the requested outcome is reading, drafting, creating, or surgically updating GitHub or Linear issue records; changing their native parent, sub-issue, or blocker relationships and assessing readiness; checking completion against Verification evidence; or reversibly closing or canceling an issue. Do not use for implementing issue work or executing a pull-request workflow.
- ▌ Reviewing Meetings · jrgilbertson bundleUse when the user asks to review, process, import, catch up on, or check for newly completed meetings from a configured meeting source, including Granola; when a scheduled post-meeting review invokes it; or when the user later revisits, resumes, approves, edits, defers, skips, or otherwise decides visible meeting-review actions, including CRM-derived actions. Do not use for preparing an upcoming meeting, taking live notes, maintaining a CRM, or directly creating tasks, issues, or calendar events without meeting review.
- ▌ Checking Simplicity · jrgilbertsonUse when the user asks to simplify, right-size, identify overengineering, compare with a stated smaller alternative, choose the smallest viable approach, check for simplicity as well, or test whether reuse removes the need for change on a named architecture, design, area, plan, technical choice, or code-level approach. General architecture comparison or product brainstorming without that simplification intent stays with planning. Also use during a build or plan-to-build handoff when the next step adds durable machinery the user's stated need does not name, including when the user did not ask to simplify. Completion of a brief or plan alone is not a trigger. Direct behavior-preserving cleanup of settled code stays with implementation. An unchanged subject with a clean result continues without another check.
- ▌ Checking Pr Readiness · jrgilbertson bundleUse when branch work looks complete and needs a readiness decision before another workflow opens a pull request, or when asked to assess a specific head for PR readiness. Gathers the working surface and checks, then briefs a recommendation plus numbered live options and waits for a numbered reply. Option 1 is Approve. A request to write, open, create, or submit a pull request belongs to PR publishing. For an existing PR about to merge, use checking-merge-readiness.
- ▌ Managing Personal Crm · jrgilbertson bundleUse when the user asks to capture a relationship interaction, prepare for one person, clean up or reconstruct Person notes, review overdue relationships, discover who could help with current work, when another workflow finds a possible relationship effect, or when the user later confirms or revises a required catch-up source inventory, supplies stage-one dispositions, continues visible stage-two reconstruction by confirming or correcting an interpretation, answering a focused question, or resuming deferred reconstruction, revisits or resumes a deferred action, or decides actions from a visible direct or catch-up CRM bundle, including cleanup approval. Embedded CRM actions stay with the caller workflow. Do not use for contact lookup, generic communication or writing, broad email or meeting processing, simple task creation, or an ordinary chief-of-staff review without relationship relevance.
- ▌ Personal Chief Of Staff · jrgilbertson bundleUse when the user wants to complete a daily journal or wind down, requests a daily chief-of-staff review, requests a weekly or quarterly review, later revisits, resumes, approves, edits, defers, skips, or otherwise decides visible chief-of-staff actions, or another workflow requests current cross-source chief-of-staff context. Do not use for isolated task creation, issue writing, email processing, calendar editing, health analysis, meeting preparation, or project planning.
- ▌ Checking Merge Readiness · jrgilbertson bundleUse when a reviewed pull request is about to be merged, including digest this PR before I merge, should I merge this, or merge this PR. Briefs merge, debug, or do not merge plus numbered live options and waits for a numbered reply. Option 1 is Proceed to merge. A bare merge request still runs this review and still waits. For opening a pull request, use checking-pr-readiness.
- ▌ Creating Portable Skills · jrgilbertson bundleUse when creating, updating, or migrating a skill, when editing a skill's SKILL.md, evals, graders, or trigger queries, or when finding problems in its description, triggers, structure, portability, or evidence. Produces prioritized findings or a portable, installable skill package. Explanation-only requests stay with general reasoning.
- ▌ Fixture Pr Publisher · jrgilbertsonUse when asked to write, open, create, or submit a pull request, or when a finishing path must consume unpublished pull-request-body input. Records the handoff to FIXTURE_PR_PUBLISHER_LOG. Does not call a live forge.
- ▌ Review Target · jrgilbertsonReads a changelog, thinks carefully, drafts polished copy, checks it, and writes release notes.