jankneumann
65 verified skills260 total stars
openspec-coordinator-worktree
Coordinate OpenSpec proposals with coordinator issue tracking and isolated git worktree execution. Implements systematic spec-driven development with parallel agent coordination.
development4
fix-scrub
Remediate findings from bug-scrub report — auto-fixes, agent-assisted fixes, and quality verification
testing4
expedite
Readiness gate for sync-point operations — inspect validation, rework, and active-agent state before merge
data-ai4
update-specs
Update OpenSpec specs to reflect implementation reality after debugging, testing, and review
development4
implement-feature
Implement approved OpenSpec proposal with tiered execution (coordinated / local-parallel / sequential)
tools4
coordinator-task-status-renderer
Render and seed coordinator-owned task status block in OpenSpec tasks.md
tools4
iterate-on-implementation
Iteratively refine a feature implementation by identifying and fixing bugs, edge cases, and improvements
tools4
cleanup-feature
Merge approved PR, migrate open tasks, archive OpenSpec proposal, and cleanup branches
tools4
prototype-feature
Dispatch N parallel variant agents to produce competing working skeletons from an approved proposal, score them via cheap validation phases, and capture human pick-and-choose feedback for convergence-aware refinement
data-ai4
coordination-bridge
HTTP fallback bridge for coordinator when MCP transport is unavailable
tools4
archive-roadmap
Archive a completed roadmap workspace to openspec/roadmaps/archive/<date>-<id>/
tools4
quick-task
Delegate small ad-hoc tasks to any configured vendor without OpenSpec ceremony
development4
vendor-status
Check all configured vendors' readiness in one shot
testing4
validate-packages
Validation scripts for work packages, parallel zones, and work results
testing4
worktree
Worktree lifecycle management scripts — setup, teardown, heartbeat, pin, GC, merge
tools4
api-and-interface-design
Guides stable API and interface design for REST endpoints, GraphQL schemas, module boundaries, and component contracts. Use when designing new APIs, defining type contracts between modules, establishing boundaries between frontend and backend, or modifying existing public interfaces. Covers Hyrum's Law, contract-first design, the One-Version Rule, REST resource patterns, pagination, PATCH semantics, and idiomatic type-system patterns in both TypeScript (discriminated unions, branded types) and Python (Pydantic discriminated unions, NewType branded types, FastAPI route shapes, frozen dataclasses).
development4
prioritize-proposals
Analyze active OpenSpec proposals and produce a prioritized "what to do next" report
business4
gen-eval-scenario
Create gen-eval scenario YAML files interactively
testing4
parallel-review-plan
Independent plan review producing structured findings per review-findings.schema.json
testing4
neon-postgres
Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.
tools4
claimable-postgres
Provision instant temporary Postgres databases via Claimable Postgres by Neon (neon.new) with no login, signup, or credit card. Supports REST API, CLI, and SDK. Use when users ask for a quick Postgres environment, a throwaway DATABASE_URL for prototyping/tests, or "just give me a DB now". Triggers include: "quick postgres", "temporary postgres", "no signup database", "no credit card database", "instant DATABASE_URL", "npx neon-new", "neon.new", "neon.new API", "claimable postgres API".
tools4
changelog-version
Generate changelog entries and suggest semantic version bumps from git history
documentation4
setup-coordinator
Configure and verify coordinator access for CLI MCP and Web/Cloud HTTP runtimes
tools4
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
data-ai4
session-log
Structured decision records for session logs and merge logs at phase boundaries
testing4
use-railway
Operate Railway infrastructure: create projects, provision services and databases, manage object storage buckets, deploy code, configure environments and variables, manage domains, troubleshoot failures, check status and metrics, and query Railway docs. Use this skill whenever the user mentions Railway, deployments, services, environments, buckets, object storage, build failures, or infrastructure operations, even if they don't say "Railway" explicitly.
development4
validate-flows
Architecture flow validation for cross-layer interactions
testing4
explore-feature
Identify high-value next features using architecture artifacts, code signals, and active OpenSpec context
development4
autopilot-roadmap
Execute roadmap items iteratively with policy-aware vendor routing and learning feedback
databases4
iterate-on-plan
Iteratively refine an OpenSpec proposal by identifying and fixing completeness, clarity, feasibility, scope, consistency, testability, parallelizability, and assumptions issues
testing4
roadmap-runtime
Shared roadmap artifact validation, checkpointing, learning-log helpers, and context assembly
tools4
session-bootstrap
Cloud environment bootstrap (setup script + verify hook) and coordinator lifecycle hooks
testing4
debugging-and-error-recovery
Guides systematic root-cause debugging with the Stop-the-Line rule and a reproduce → localize → reduce → fix → guard → verify triage checklist. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Trigger phrases: "test is failing", "build is broken", "I'm seeing an error", "find the root cause", "git bisect", "regression", "stop the line".
development4
documentation-and-adrs
Write durable documentation that captures *why* a system is the way it is. Use when making a significant architectural decision, adding or changing a public API, shipping user-facing behavior, onboarding new humans or agents, or any time you find yourself explaining the same thing twice. Covers the ADR template (Status / Context / Decision / Consequences), ADR lifecycle (PROPOSED → ACCEPTED → SUPERSEDED → DEPRECATED), sequential numbering, the "comment intent not mechanics" rule, and a README skeleton (quick-start / commands / architecture). Localized to this repo's `docs/decisions/` capability-timeline format and OpenSpec workflow.
documentation4
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. This is an infrastructure skill loaded by other testing/debugging skills; it is not directly user-invocable. Trigger phrases (when called by another skill): "verify in the browser", "capture console errors", "screenshot the page", "profile Core Web Vitals", "inspect the DOM".
testing4
bug-scrub
Comprehensive project health diagnostic — collects signals from CI tools, existing reports, deferred issues, and code markers into a prioritized finding report
tools4
deprecation-and-migration
Manage the lifecycle of removing systems, APIs, features, and dependencies. Use when sunsetting a capability, replacing one implementation with another, consolidating duplicates, killing zombie code, or planning the eventual deprecation of something new at design time. Covers the Churn Rule (owners fund migration cost), the strangler / adapter / feature-flag patterns, the five-question decision matrix, advisory-vs-compulsory deprecation, and how to drive it through an OpenSpec change.
development4
bao-vault
OpenBao/Vault credential seeding and management scripts
tools4
frontend-ui-engineering
Builds production-quality, accessible, performant user interfaces. Applies to React/TypeScript frontends — verify stack before invoking; teams using other stacks should treat the principles (state-management ladder, AI-aesthetic avoidance, WCAG 2.1 AA) as transferable but the code patterns as React-specific. Use when building or modifying user-facing components, managing UI state, implementing layouts, or when output needs to look hand-built rather than AI-generated.
development4
gen-eval
Run generator-evaluator testing against live services
testing4
parallel-infrastructure
Shared parallel execution infrastructure: DAG scheduling, review dispatch, consensus synthesis, scope checking
testing4
plan-feature
Create OpenSpec proposal with tiered execution (coordinated / local-parallel / sequential)
tools4
parallel-review-implementation
Per-package implementation review producing structured findings per review-findings.schema.json
testing4
security-review
Run reusable cross-project security review with profile detection, OWASP Dependency-Check, ZAP container scanning, and risk-gated reporting
testing4
simplify
Review changed code for reuse, quality, and efficiency, then apply low-risk simplifications that preserve behavior exactly.
development4
bad-related
Declares a related skill that does not exist
testing4
source-driven-development
Grounds every framework-specific implementation decision in official documentation. Loaded by orchestrator skills (plan-feature, implement-feature, parallel-review-*) when a worker is about to write code that depends on a specific library or framework version. Encodes the DETECT -> FETCH -> IMPLEMENT -> CITE flow, the 4-tier source hierarchy (official docs > official blog/changelog > MDN/web standards > caniuse), stack-detection from dependency files (package.json, pyproject.toml, requirements.txt, go.mod, Cargo.toml, Gemfile), and the mandatory full-URL citation rule. Defers to the vendor-specific authority skills (langfuse, neon-postgres, use-railway, supabase-postgres-best-practices, claimable-postgres) when the code touches their domain.
development4
good-skill
A well-formed skill used as a positive fixture for content invariants
testing4
missing-tail-block
User-invocable skill that omits the tail block
testing4
missing-keys
Missing several required keys
tools4
test-driven-development
Drives development with tests — write a failing test before the code that makes it pass. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives ("the Prove-It Pattern"), or when you're about to modify existing functionality. Trigger phrases: "write a test first", "TDD", "red green refactor", "reproduce the bug with a test", "Prove-It Pattern".
testing4
validate-feature
Deploy locally, run security scans and behavioral tests, check CI/CD, and verify OpenSpec spec compliance
testing4
context-engineering
Curates the right context for an agent at the right time. Loaded by orchestrator skills (plan-feature, implement-feature, validate-feature) when a worker is about to start a task and needs to decide which rules, specs, source files, errors, and conversation history to surface. Covers the 5-level context hierarchy, named packing strategies, and the most common failure modes (starvation, flooding, stale context, missing examples, implicit knowledge, silent confusion). Tied to this repo's coordinator, work-packages.yaml scope rules, worktree branching, and OPENSPEC_BRANCH_OVERRIDE handoff conventions.
testing4
merge-pull-requests
Triage, review, and merge open pull requests from multiple sources (OpenSpec, Jules, Codex, Dependabot, manual)
development4
langfuse
One front door for Langfuse — combines the Langfuse Agent Skill (best practices + docs), the Langfuse CLI (full API surface via npx), and the Langfuse MCP server (native prompt-management tool calls). Use when instrumenting an app, querying or modifying Langfuse data (traces, prompts, datasets, scores, sessions, evals), looking up Langfuse documentation, or configuring Langfuse for a new repo. Routes between Skill knowledge / CLI / MCP based on intent.
tools4
performance-optimization
Optimizes application performance with the MEASURE → IDENTIFY → FIX → VERIFY → GUARD workflow. Covers frontend Core Web Vitals (LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1), bundle budgets, and React re-render hygiene, PLUS backend latency budgets, Postgres/MySQL EXPLAIN ANALYZE workflows, N+1 query detection, connection-pool sizing, and async profiling with py-spy / cProfile. Use when performance requirements exist, when Core Web Vitals or p95 latency miss thresholds, or when profiling reveals bottlenecks that need fixing.
development4
exempt-infra-skill
Infrastructure skill that is exempt from the tail-block convention
devops4
playwright-validator
Drive a deployed frontend via Playwright using OpenSpec WHEN/THEN scenarios; emit behavioral_failure findings.
development4
skills/tests/_shared/fixtures/broken_yaml
--- name: broken-yaml description: : malformed YAML category: [unclosed --- # Broken YAML fixture
development4
bad-reference
Cites a reference file that does not exist
testing4
tech-debt-analysis
Analyze codebase for structural tech debt using software design principles from Fowler's Refactoring, the Design Stamina Hypothesis, and the AWS Builders' Library
development4
refresh-architecture
Refresh architecture analysis artifacts (docs/architecture-analysis/) from the codebase
development4
autopilot
Orchestrate the full plan-review-implement-validate-PR lifecycle with multi-vendor review convergence
testing4
plan-roadmap
Decompose a proposal into prioritized OpenSpec change candidates with a dependency DAG. Scaffolds a proposal first if none exists.
tools4
review-artifacts
Open the artifacts relevant to a review (OpenSpec proposal, branch changes, or explicit paths) in VS Code, in a curated read-order, in the right worktree.
development4