Product & Planning

kennyolofsson23-netizen Bundle

Align any project with Kenny's global Claude Code setup. Audits test coverage, CI/CD, security, skills usage, and creates a prioritized quality roadmap. Use when opening a project for the first time, after a global setup change, or when the user says "align", "bring up to speed", "audit this project", "quality check", or "what's missing".

korchasa Bundle

Use when the user asks to plan a LARGE feature that spans multiple sessions or phases — produces an epic under the `tasks` role from AGENTS.md with dependency-ordered phases, atomic tasks, and per-phase status tracking. Use plan for single-session tasks. Do NOT trigger on generic planning, roadmap, or brainstorming requests.

korchasa Bundle

Produce a comprehensive Product Requirements Document (PRD) for a product feature. Use when the user asks to write a PRD or formalize a product feature's scope, goals, user value, and success metrics. Not for internal technical/engineering change proposals (those argue for a code/architecture change, not a product feature).

zinohome Bundle

Plan and organize software development tasks effectively. Use when breaking down features, creating user stories, or planning sprints. Handles task breakdown, user stories, acceptance criteria, and backlog management.

lofcz Skill

Define or update Plate editor-behavior specs with a pass-gated, evidence-scored plan. Use for behavior law, authority maps, protocol rows, parity gates, research-backed winner shifts, editor chrome contracts, and implementation-roadmap changes.

lofcz Skill

Triage and process the Slate v2 issue ledger with OpenClaw-style sweep discipline: archive-first discovery, duplicate proof, small-fix gates, exact claim rules, maintainer-safe issue output, and gitcrawl API refreshes.

cody-hutson Bundle

The voice of the PMO — produces audience-calibrated, ready-to-send communications. Covers email, Teams, Confluence, exec briefs, meeting agendas, escalation drafts, recaps, and status updates. Use when drafting any stakeholder communication. Triggers: "draft an update for [audience]", "write the exec brief", "prepare the agenda", "send the escalation email", "write the recap", "put together a message", "write a Teams post."

cody-hutson Bundle

Runs Stage-2 Triage over the platform's improvement backlog — reads `status: proposed` GitHub Issues, executes the Phase-A analysis sequence (A1–A6.5: DoR completeness, duplicate/subsumption + similarity, dependency-state validation + native-dep mirror, feasibility, priority re-evaluation, oversize routing, per-issue summary, management-task signals), and produces ONE consolidated triage summary with a per-issue Approve/Defer/Reject recommendation. Auto-execute is the operative default: the A1–A6 enrichment runs end-to-end without per-action approval; only the state-mutating Close/Reject requires operator confirmation, and the Approve/Defer/Reject verdict itself stays operator-only (Tier 3). Reads the pipeline improvement backlog, not the Jira / project delivery backlog. Triggers: "triage the proposed queue", "run Stage-2 triage", "triage the improvement backlog", "run the triage analysis on the proposed issues", "what's the triage recommendation for the proposed backlog".

cody-hutson Bundle

Plans the PMO platform release lifecycle. Modes: Backlog analysis · Release planning · Dry run · Pattern review (draft). Analyzes the improvement backlog, maps dependencies, suggests release bundles, generates release plans, and produces dry-run diffs. Read-only — never modifies governance files. Triggers: "analyze the improvement backlog", "bundle the milestone", "generate the release plan", "produce the dry-run diff", "what's in v[X.Y]".

cody-hutson Bundle

Keeps the living initiative roadmap current as work arrives — the ongoing roadmap-grooming function. Classifies new or changed issues into the ratified initiative → capability-slice → horizon, syncs the operator's board fields + roadmap §3, and surfaces two-surface drift. Surface-agnostic: references the board via registered depersonalization tokens only, never a literal board id. Modes: Incremental Maintenance · Re-baseline · Drift Audit. Triggers: "groom the roadmap", "classify this issue into the roadmap", "place this on the roadmap", "re-baseline the initiative set", "audit roadmap drift", "is the roadmap in sync", "keep the roadmap current."

cody-hutson Bundle

Product Owner Specialist — owns the WHAT and the WHY of the backlog: value framing, prioritization, story authoring with acceptance criteria, and the accept/reject decision. Operates at the backlog tier, deciding which item is most valuable to build next and whether its value is accepted. Composes pmo-process-designer (story/requirement authoring, INVEST scoring, Given-When-Then acceptance criteria) + delivery-engine (backlog health, DoR readiness, sprint-scope fit) — invokes them, never re-implements them. Modes: Backlog Prioritization · Story Authoring & Acceptance · Backlog Readiness · Value & Scope Decision. Use when the question is what to build next, how to value-rank the backlog, whether a story's acceptance criteria are accepted, or whether to include / defer / cut scope by value. Triggers: "prioritize the backlog", "what's most valuable", "rank these stories", "is this ready to pull", "should we build or defer X", "write the story and acceptance criteria for [value]", "accept this story".

cody-hutson Bundle

Program Manager Specialist — drives a program's multiple coordinated workstreams to outcomes, deciding which cross-project signal moves the delivery plan and binding the program's risk posture to its delivery decisions. Operates at the program tier above any single project's delivery and below portfolio strategy, across agile and waterfall governance. Composes ppm-agent (strategic synthesis + intake-governance) + delivery-engine (backlog→release-readiness mechanics) — invokes them, never re-implements them. Modes: Cross-Project Risk & Dependency Synthesis · Program Delivery Posture · Program Release-Readiness · Program Intake & Capacity Trade-off · Program RAID & Decision Stewardship. Use when one program's multi-workstream delivery needs a risk read, a posture call, a go/no-go, an intake trade-off, or RAID stewardship. Triggers: "coordinate the program's workstreams", "program capacity trade-off", "cross-workstream dependency call", "program posture on delivery", "who owns this program outcome".

cody-hutson Bundle

Project Manager Specialist — owns a single named project's delivery end-to-end at the single-project tier (not a program or portfolio): renders the project's go/no-go, owns its RAID, stewards its milestone. Composes delivery-engine only — invokes it across modes A/C/D/E/F/G, never re-implements it; the value-add is single-project delivery accountability plus cross-mode coherence within delivery-engine (a DoR gap conditioning the sprint plan, a DoD failure originating a RAID entry). Modes: Project Backlog & Readiness Health · Project Sprint Planning & Execution · Project Release-Readiness (DoD) · Project RAID & Decision Stewardship. Use when one named project needs its delivery owned. Triggers: "who is accountable for this project", "this project's go/no-go call", "project schedule stewardship", "project-level blocker escalation", "single-project delivery ownership". Routes program / multi-workstream requests to pmo-program-manager; routes ceremony-facilitation requests to pmo-scrum-master.

cody-hutson Bundle

Business Analyst Specialist — owns the HOW-it-works of delivery: requirements elicitation, process/workflow documentation, traceability, and gap analysis. Operates at the requirements tier: eliciting what the business needs, documenting how work flows, and proving the requirement traces from source to evidence. Composes pmo-process-designer (requirements definition, INVEST, Given-When-Then, process docs, traceability, gap analysis) + delivery-engine (backlog substrate, DoR readiness) — invokes them, never re-implements them. Modes: Requirements Elicitation · Workflow & Process Documentation · Traceability & Coverage · Gap Analysis. Use when the question is what the business needs elicited, how a process is documented, whether a requirement traces end-to-end, or where the coverage gap is. Triggers: "act as the business analyst", "elicit what the business needs", "BA judgment on this stakeholder ask", "whose business need is this", "own the current-state and future-state picture".

ed3design Skill

Use when the code-review-backlog is large (>30 commits OR >5,000 LoC changed since last review) AND the caller has Agent/Task-tool dispatch capability (.e., top-level orchestrator or main Claude session). Trigger on phrases like "code-review backlog is big", "no review for weeks", "many commits without review", "review of 100+ commits", "how do I review these 200 commits", "chunk review", "parallel code-reviewer subagents". Do NOT load for single-PR review (use superpowers:requesting-code-review directly), for <30-commit backlog (single subagent suffices), for non-Git codebases (chunking-by-SHA-range presumes git workflow), or when running as a subagent yourself without Agent-tool access (the chunk-dispatch pattern is then unexecutable — use risk-based-triage instead, documented in the skill's Fallback section). Complements (sub-of) `superpowers:requesting-code-review` and `superpowers:dispatching-parallel-agents`.

ed3design Skill

Use when a `git push` is blocked by a pre-push hook (freshness/lint/test/data-pipeline) AND the blocking condition is provably orthogonal to the commits being pushed (different subsystem, different pipeline, known pre-existing issue). Trigger on phrases like "pre-push hook blocks", "--no-verify with justification", "hook drift", "freshness check failed", "push aborted but code is OK", "should use --no-verify". Produces (1) orthogonality check before bypass, (2) audit-trail entry in the Daily Note with reason + blocking issue + backlog reference, (3) a separate backlog item for the blocking issue, (4) the `--no-verify` push only after these are done. Do NOT load when the hook block is directly related to the commits, when no Daily Note exists, when bypass has not been explicitly approved by the user, or when the blocking issue is critical/security.

ed3design Skill

Use when the user/agent is about to push code, merge a feature branch, or claim work as "done" AND no code-review has happened recently. Specifically trigger when ANY hold: >7 days since last `requesting-code-review` invocation, >30 atomic commits accumulated since last review, >5000 LoC changed, pre-push-hook code-review-warning bypassed ≥2 times in succession, or the user says "haven't done a review in weeks", "I'll just push this", "the hook is only a warning, ignore it", "it's just a small fix on top". STOP and surface a cost-estimate-warning BEFORE the push — quantify expected backlog cost (wallclock + tokens + re-review cycles) and offer chunked-parallel-review-dispatch as alternative. Do NOT load for fresh branches (≤3 commits, ≤500 LoC, ≤2 days), explicitly-marked WIP pushes, inside an active review session, or one-line typo/doc commits.

ed3design Skill

Use when the user presents a loose collection of items (a brain-dump, an inbox-list, a "I want to do all of these" list, scattered TODOs) and wants help turning it into an actionable plan — phases with dependencies, entry triggers, and confirmation questions on each meaningful design decision. Trigger on phrases like "I have a few things here", "clean up the brain-dump", "how do I tackle all this", "roadmap from these items", "consolidate the inbox", "I don't know where to start", "make me a plan out of this", "consolidate this list into a plan", "turn this dump into a roadmap". Do NOT load when the user already has a phase plan and wants to execute it (use gsd:gsd-execute-phase), when there is a single concrete task (just do it), or for design exploration where the items are not yet committed work (use design-first-iteration). Complements gsd:gsd-new-milestone and gsd:gsd-plan-phase — this skill bridges the gap *before* either of those, when items are still unstructured and clusters are not yet visible.

ed3design Skill

Use when an externally-commissioned advisor output (energy-consultant roadmap/iSFP, PV quote, renovation quote, tax-advisor note, expert report, investment recommendation) needs evaluation — do NOT accept the numbers at face value, run a structured 5-step audit: (1) inventory reality-check, (2) sequence/legal-check against applicable law, (3) cost/market-check against realistic values, (4) completeness-check (implied-but-not-costed components), (5) motive-check (advisor incentives, double application, kickback risk). In one real case this surfaced 6 technical defects plus an apparent subsidy-fraud construct. Trigger on phrases like "review this iSFP", "run the numbers on this quote", "the tax advisor says", "how should I evaluate this offer", "should I adopt this proposal". Do NOT load for the user's own data analysis, for pure market research (no concrete offer), or for legally-mandated expert reports (structural engineer, chimney sweep — a different audit mode).

ed3design Skill

Use BEFORE writing any SQL WHERE-clause that filters on a string/enum-typed column. Schema-verify via `\d <table>` shows COLUMN TYPE (text/varchar/enum) but NOT the actual values used. Code may set 'taken' while the reviewer thinks 'accept'. Pattern: run `SELECT DISTINCT <col> FROM <table>` (or grep for `_update_<col>`-style setters) to discover the actual value-set BEFORE formulating WHERE. Without this discovery step, queries silently return wrong counts: rows matching the real value get excluded, user sees "0 results" while reality has many. Trigger on phrases like "how many entities with status X exist", "user_response='accept'", "SELECT ... WHERE enum_col=...", "why am I seeing no hits", "forensic DB analysis", "cockpit filter shows 0". Do NOT load for known well-defined PostgreSQL ENUM types where `\d` shows values inline, first-time-CREATE-TABLE queries, or non-text/non-enum columns.

ed3design Skill

Use before executing any superpowers/gsd-style implementation plan (`docs/superpowers/plans/*.md`, `.planning/PLAN.md`, `roadmap-phase-*.md`) whose plan-file was written in a previous session — to detect whether tasks have already been implemented (in a parallel session, by a different agent, or by the user) before re-executing them. Trigger on phrases like "start plan execution", "apply executing-plans skill", "gsd-execute-phase", "execute phase", "plan file is from yesterday/last week", "plan written earlier, now executing". Without `git log <base>..HEAD` precheck, completed tasks can be re-implemented inline, wasting significant time. Do NOT load for plans written in the SAME session (no drift possible), plans without git-tracked code targets (pure-documentation phases), or when the user explicitly states "the codebase is at the pre-plan state".

ed3design Skill

Captures a pattern from a Phase-A execution session: when executing a roadmap phase from a knowledge vault that was designed days/weeks ago AND a previous session may have prepared draft artifacts (service maps, status files, execution guides), verify each item against current reality (DB queries, docker inspect, systemctl, filesystem) BEFORE applying changes. Find drift in pre-existing files; document discoveries that turn a routine item into an issue; never check a roadmap item as done just because the roadmap said so. Trigger on phrases like "implement Phase X", "execute roadmap item", "implement Phase A of … consolidation", "item Y from the roadmap", "execute the phase from the vault". Do NOT load for fresh roadmap design (use brain-dump-to-phased-roadmap), for executing a freshly-written task list with no vault history, or for non-vault roadmaps.

archieindian Bundle

Diagnoses silent skill discovery failures — YAML parse errors, path violations, schema mismatches — so broken skills don't disappear without a trace.

archieindian Bundle

Analyzes skill descriptions for trigger quality — scores clarity, keyword density, and specificity, then suggests rewrites that improve discovery accuracy.

harness Bundle

Generates Liquibase database changesets via a structured workflow: resolve schema+instance (from context or via API discovery), confirm DB engine type, generate Liquibase YAML, and present for HITL review with Accept / Deny / Accept & Commit actions. Supports update mode (refine existing changeset) and error-recovery mode (fix a failed migration).

mattjaikaran Skill

Use when you need Meridian to codebase Audit & Work Discovery.

mattjaikaran Skill

Use when you need Meridian to backlog Seed Management.

mattjaikaran Skill

Use when you need Meridian to cross-Milestone Roadmap.

greglas75 Bundle

B2B lead discovery and enrichment skill. Finds company addresses, employee emails, and phone numbers filtered by industry, geography, role, and company size. 100% free-tier: orchestrates Claude Code's native WebSearch and WebFetch plus free OSINT subprocesses (theHarvester, crt.sh, whois, GitHub API, OSM Overpass, DNS MX, bash SMTP probe). No paid API keys required — optional env vars (ZUVO_HUNTER_KEY, ZUVO_APOLLO_KEY, ZUVO_GITHUB_TOKEN) are recognized as enhancers but never required. Hybrid mode: supplying --domains triggers enrichment; --industry + --geo triggers discovery. Interactive checkpoints after Phase 1 and Phase 2. Output: CSV + JSON + Markdown in docs/leads/. Optional --gdpr-strict for EU/EEA compliance.

greglas75 Skill

Engineering retrospective from git metrics. Reports deployment frequency, release cycle span, churn hotspots, backlog health. Outputs narrative report with 3+ actionable items. Flags: --since, --path, explicit range argument.

greglas75 Skill

Manage the project's tech debt backlog. Add, list, fix, wontfix, delete, prioritize, and suggest batch actions on tracked issues. Used by audit and review skills to persist findings, and directly by users to manage accumulated debt. Modes: list [category], add [description], fix B-{N}, wontfix B-{N} [reason], delete B-{N}, stats, prioritize, suggest.

greglas75 Bundle

SEO/GEO site audit covering 13 dimensions with 6 critical gates. Scans source code, templates, and config files across meta tags, structured data, AI crawlers, content quality, GEO readiness, performance, and optional live Core Web Vitals. Framework-aware: Astro, Next.js, Hugo, WordPress, React, plain HTML. Flags: full (default), [path], --live-url <url>, --quick, --content-only, --geo, --profile <marketing|docs|blog|ecommerce|app-shell>, --content-profile auto|marketing|docs|blog|ecommerce|app-shell, --live-sample-bots <default|all|bot1,bot2>, --persist-backlog.

greglas75 Bundle

Write tests for existing production code. Processes ONE file at a time through a full pipeline: analyze, inventory (frozen BEFORE writing), write, executable coverage gate, verify, blind coverage audit, adversarial review, log. Uses CodeSift for discovery and analysis when available. Modes: [path] (specific target), auto (discover and loop until done), --dry-run (plan only; skips suite verification).

greglas75 Skill

Architecture skill with three modes: review existing codebase architecture (A1-A9 dimensions), create Architecture Decision Records, or design new systems from requirements. Modes: --mode review [path], --mode adr, --mode design. Uses CodeSift for module discovery, dependency mapping, structural metrics, and temporal coupling detection.

greglas75 Bundle

Content file quality audit across 8 dimensions (CC1-CC8): encoding artifacts (NBSP, mojibake, zero-width), markdown syntax (broken italic, orphan backslash), CMS migration artifacts (Joomla/WordPress/PHP), frontmatter quality, image integrity, link integrity with anchor validation, content completeness, and spelling/typography. Language-agnostic with multi-encoding mojibake detection. Companion fix skill: content-fix. Flags: [path], --live-url <url>, --quick, --content-path <dir>, --lang <code>, --check-external, --profile <type>, --persist-backlog.

greglas75 Bundle

Expand and optimize existing articles. Adds new sections, deepens thin content, and applies the same quality pipeline as write-article (anti-slop, BLUF, GEO signals, humanization, multi-schema). Includes web search research about the topic and auto-discovery of internal links from your content collection. Replaces content-optimize. Flags: [file], --dry-run, --lang, --tone, --site-dir, --domain, --skip-research, --light.