patch-engineer
Patch engineer persona focused on security fix quality, code correctness, testing strategies, and regression prevention
Patch engineer persona focused on security fix quality, code correctness, testing strategies, and regression prevention
WHEN to auto-invoke: Finishing tasks, claiming "done" or "complete", before marking work finished, when asserting code works, wrapping up implementations. WHEN NOT to invoke: During active development, exploration phases, planning discussions, research tasks.
This skill provides an advanced financial modeling suite with DCF analysis, sensitivity testing, Monte Carlo simulations, and scenario planning for investment decisions
Score concepts on impact/delight/effort and pick a 1-day spike.
Tech Lead role in AID methodology. Use for architecture decisions, code reviews, technical direction, operational readiness, team guidance.
Review task artifacts (task-mapping, tasks.md) for quality and completeness. Use when reviewing task phase outputs, finding gaps in task planning, or when you see "review mapping", "review tasks", "task quality", or "cycle review".
Build, test, and manage mcpGraph tools using the mcpGraphToolkit MCP server. Discover MCP servers and tools, construct graph nodes with JSONata and JSON Logic, and interact with mcpGraph configurations. IMPORTANT: Always read this file before creating graph tools using mcpGraphToolkit.
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
Intelligent workspace cleanup using multi-signal detection (similarity, timestamps, references) to identify and archive clutter with two-stage safety review
Conduct effective daily standup meetings for agile teams. Use when facilitating standups, tracking blockers, or improving team synchronization. Handles standup format, time management, and blocker resolution.
이 스킬의 목적과 언제 사용하는지 간단히 설명합니다. 주요 기술과 시나리오를 포함하세요.
Help neurodivergent users break down overwhelming tasks into manageable steps. Use when tasks feel paralyzing, when executive function is struggling, when someone can't start, or when the Wall of Awful has built up. Applies ADHD/autism-aware decomposition strategies.
Use when selecting between MCP tools based on task complexity and requirements - provides a structured selection workflow and decision rationale.
AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.
Decision transparency, feedback collection, and debate invitations for AID methodology. Active in ALL phases for ALL roles.
Build, test, and manage mcpGraph tools using the mcpGraphToolkit MCP server. Discover MCP servers and tools, construct graph nodes with JSONata and JSON Logic, and interact with mcpGraph configurations. IMPORTANT: Always read this file before creating graph tools using mcpGraphToolkit.
AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
Execute Preflight phase for /itp:go workflow - create ADR (MADR 4.0), design spec from global plan, verify checkpoint. Use when creating ADRs, design specs, or when /itp:go invokes Preflight phase. Triggers - ADR creation, design spec, MADR format, preflight verification.
Implements file-based planning for MAP Framework workflows with branch-scoped task tracking in .map/ directory. Prevents goal drift via automatic plan synchronization before tool use and validates completion state on exit.
Use when facing complex engineering challenges that require systematic methodology - horrible bugs, safe refactoring, code review, production incidents, technical debt decisions, or building confidence in unfamiliar codebases
Threat modeling workflow for software systems: scope, data flow diagrams, STRIDE analysis, risk scoring, and turning mitigations into backlog and tests
Estimate software development tasks accurately using various techniques. Use when planning sprints, roadmaps, or project timelines. Handles story points, t-shirt sizing, planning poker, and estimation best practices.
PM role in AID methodology. Use for requirements, user stories, acceptance criteria, stakeholder management, scope definition.