issue-driven-development

Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work

Use when writing code in typed languages - enforces full typing with no any/unknown/untyped escapes, even if it requires extra time

Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language

Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement

Use before merging PR - final gate ensuring all tests pass, review complete, CI green, and acceptance criteria verified

Entry point for ALL work requests - triages scope from trivial to massive, asks clarifying questions, and routes to appropriate planning skills. Use this when receiving any new work request.

Use to spawn isolated worker processes for autonomous issue work. Creates git worktrees, constructs worker prompts, manages PIDs, and handles worker lifecycle.

Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue

Use after code review - implement ALL recommendations regardless of severity; no finding is too minor to address

Use when starting any work session - establishes autonomous operation mode, overriding token limits and time pressure to work until goal is achieved

Use when user confirms autonomous operation across multiple issues. Orchestrates parallel workers, monitors progress, handles SLEEP/WAKE cycles, and works until scope is complete.

Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base

Monitors CI/PR status for orchestration. Implements SLEEP/WAKE patterns via polling, hooks, and webhooks. Handles CI failures and auto-merge.

Use after creating PR - monitor CI pipeline, resolve failures cyclically until green or issue is identified as unresolvable

Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point

Use after implementing features - 7-criteria code review covering blindspots, clarity, maintainability, security, performance, documentation, and style

Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity

Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessions

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.

Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state

Use when writing code, documentation, or comments - always use accessible and respectful terminology

Use for MASSIVE work requests requiring multi-epic planning. Creates research spikes, documents all unknowns and decisions, builds resumable architecture documents, and structures work into epics and milestones.

Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code

IPv6 is THE first-class citizen. All code, tests, documentation, and configurations MUST be IPv6-first. IPv4 MAY be added only for legacy support as a second-class citizen.

Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units

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

Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end

Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning

Use to maintain context across sessions - integrates episodic-memory for conversation recall and mcp__memory knowledge graph for persistent facts

Use for time-based grouping of issues into delivery phases. Creates, updates, and tracks milestones, associates issues and epics, monitors progress toward milestone completion.

Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission

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.

Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary

Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach

Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields

Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming

Use before code review - determine if change is minor (review new code only) or major (review impacted code too)

Defines context handover format when workers hit turn limit. Creates structured handover files that enable replacement workers to continue seamlessly.

Defines behavior protocol for spawned worker agents. Injected into worker prompts. Covers startup, progress reporting, exit conditions, and handover preparation.