troykelly
@troykelly
Public Skills
ci-monitoring
by troykelly
Use after creating PR - monitor CI pipeline, resolve failures, address review feedback, and merge when all gates pass
project-board-enforcement
by troykelly
MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.
worker-dispatch
by troykelly
Use to spawn isolated worker processes for autonomous issue work. Uses Task tool with run_in_background for parallel execution and TaskOutput for monitoring. Pre-extracts context to minimize worker token usage.
feedback-triage
by troykelly
Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type and priority, creates well-formed GitHub issues with proper project board integration.
issue-driven-development
by troykelly
Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification
autonomous-orchestration
by troykelly
Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers using Task tool, monitors with TaskOutput, handles SLEEP/WAKE cycles, and works until scope is complete without user intervention.
autonomous-operation
by troykelly
Use when starting any work session - establishes autonomous operation mode, overriding token limits and time pressure to work until goal is achieved
github-api-cache
by troykelly
MANDATORY before any GitHub project operations - caches project metadata to prevent rate limit exhaustion. Called by session-start. Other skills MUST use cached data.
issue-prerequisite
by troykelly
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
session-start
by troykelly
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
issue-prerequisite
by troykelly
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
feedback-triage
by troykelly
Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type and priority, creates well-formed GitHub issues with proper project board integration.
project-board-enforcement
by troykelly
MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.
epic-management
by troykelly
Use for LARGE work requiring feature-level grouping. Creates epic tracking issues, manages related issues under a common label, tracks epic progress, and coordinates with milestones.
comment-analyzer
by troykelly
Use when asked to review code comments for accuracy/quality or explicitly asked to run the comment-analyzer subagent.
comprehensive-review
by troykelly
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
code-reviewer
by troykelly
Use when explicitly asked to run the code-reviewer subagent or when another skill requires the code-reviewer agent card.
acceptance-criteria-verification
by troykelly
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
pr-creation
by troykelly
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary
inline-documentation
by troykelly
Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code
documentation-audit
by troykelly
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
error-recovery
by troykelly
Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state
pexels-media
by troykelly
Source royalty-free images and videos from Pexels API for design, placeholders, or content. Supports search, curated/popular content, collections, multiple resolutions, and ALWAYS creates detailed sidecar metadata files.
memory-integration
by troykelly
Use to maintain context across sessions - integrates episodic-memory for conversation recall and mcp__memory knowledge graph for persistent facts