Skip to content

Latest commit

 

History

History
110 lines (82 loc) · 8.81 KB

File metadata and controls

110 lines (82 loc) · 8.81 KB

All 32 skills

Complete catalog of skills in this library. Slash commands are the usual entry points; skills also activate automatically based on task type. See README — Commands for the command list.

Claude Code uses /spec, /build, … Cursor uses /sys-spec, /sys-build, … (same workflows).


Table of contents


SysPM — PM workflow

Skill What It Does Use When
syspm Mirrored SysPM PM skill with plan/structure/sync/track references You want the PM lifecycle mirrored inside this repository
pm-spec-and-prd Creates PM-first PRDs and converts PRDs into epic artifacts Starting PM planning from initiative scope before story-level engineering planning
pm-epic-decomposition Breaks an epic into T### Jira-mappable work items with dependency metadata An epic exists and needs decomposed delivery units
pm-jira-sync Syncs SysPM epic and T### artifacts to Jira and maintains local mapping Local SysPM artifacts should become Jira issues
pm-status-and-reporting Produces artifact-backed PM status updates from SysPM and Jira state Stakeholders request progress, blockers, or next PM action

Discover — Understand the codebase

Skill What It Does Use When
brownfield-discovery Map an unfamiliar codebase — architecture, conventions, key files, and risk areas — before making changes Joining a new project, onboarding to a legacy codebase, or scoping a change in unknown territory

Define — Clarify what to build

Skill What It Does Use When
idea-refine Structured divergent/convergent thinking to turn vague ideas into concrete proposals You have a rough concept that needs exploration
spec-driven-development Write a PRD covering objectives, commands, structure, code style, testing, and boundaries before any code Starting a new project, feature, or significant change
jira-spec-driven-development Jira-grounded spec workflow with mandatory Jira MCP validation, story context loading, and related-ticket context Defining work directly from Jira tickets or stories

Plan — Break it down

Skill What It Does Use When
planning-and-task-breakdown Decompose specs into small, verifiable tasks with acceptance criteria and dependency ordering You have a spec and need implementable units
jira-planning-and-task-breakdown Story-scoped planning workflow that writes plan artifacts under jira-spec/{story-id}/ Planning implementation tasks for a Jira-scoped spec

Sync Jira board — After plan, before build

Skill What It Does Use When
jira-board-sync Writes jira-spec/{story-id}/sync.md comparing current Jira story/tasks to proposed updates from spec-* / plan-* / todo-*; applies to Jira only after explicit user approval You need a reviewed diff before mutating the board

Build — Write the code

Skill What It Does Use When
incremental-implementation Thin vertical slices — implement, test, verify, commit. Feature flags, safe defaults, rollback-friendly changes Any change touching more than one file
generate-unit-tests Generates unit tests from deferred test notes and implemented behavior After build when coverage is missing or /test phase
context-engineering Feed agents the right information at the right time — rules files, context packing, MCP integrations Starting a session, switching tasks, or when output quality drops
source-driven-development Ground every framework decision in official documentation — verify, cite sources, flag what's unverified You want authoritative, source-cited code for any framework or library
frontend-ui-engineering Component architecture, design systems, state management, responsive design, WCAG 2.1 AA accessibility Building or modifying user-facing interfaces
api-and-interface-design Contract-first design, Hyrum's Law, One-Version Rule, error semantics, boundary validation Designing APIs, module boundaries, or public interfaces
mobile-app-engineering Production-quality mobile engineering for Android and iOS — architecture layers, screen states, error handling, UX discipline, platform safety Building or modifying any mobile screen, flow, repository, service, or test

Verify — Prove it works

Skill What It Does Use When
browser-testing-with-devtools Chrome DevTools MCP for live runtime data — DOM inspection, console logs, network traces, performance profiling Building or debugging anything that runs in a browser
debugging-and-error-recovery Five-step triage: reproduce, localize, reduce, fix, guard. Stop-the-line rule, safe fallbacks Tests fail, builds break, or behavior is unexpected

Review — Quality gates before merge

Skill What It Does Use When
code-review-and-quality Five-axis review, change sizing (~100 lines), severity labels (Nit/Optional/FYI), review speed norms, splitting strategies Before merging any change
code-simplification Chesterton's Fence, Rule of 500, reduce complexity while preserving exact behavior Code works but is harder to read or maintain than it should be
security-and-hardening OWASP Top 10 prevention, auth patterns, secrets management, dependency auditing, three-tier boundary system Handling user input, auth, data storage, or external integrations
performance-optimization Measure-first approach — Core Web Vitals targets, profiling workflows, bundle analysis, anti-pattern detection Performance requirements exist or you suspect regressions

Ship — Deploy with confidence

Skill What It Does Use When
git-workflow-and-versioning Trunk-based development, atomic commits, change sizing (~100 lines), the commit-as-save-point pattern Making any code change (always)
deprecation-and-migration Code-as-liability mindset, compulsory vs advisory deprecation, migration patterns, zombie code removal Removing old systems, migrating users, or sunsetting features
documentation-and-adrs Architecture Decision Records, API docs, inline documentation standards — document the why Making architectural decisions, changing APIs, or shipping features
shipping-and-launch Pre-launch checklists, feature flag lifecycle, staged rollouts, rollback procedures, monitoring setup Preparing to deploy to production
jira-shipping-and-launch Shipping workflow with mandatory Jira ticket and task comment updates during launch Releasing features where Jira ticket updates are required as part of ship phase

Ad-hoc

Skill What It Does Use When
quick-task-execution Fast, atomic changes that skip the full spec/plan cycle while still being tracked and safe One-off fixes, small improvements, or time-boxed tasks

Meta

Skill What It Does Use When
using-agent-skills Discovery flowchart and rules for which skill applies to a task Starting a session or unsure which skill to load