agile-workflow

Plugin agile-workflow from marketplace nklisch-skills in nklisch/skills. Commands read from the repo's manifest — 12 days ago.

Skills (32)

• autopilot

  Goal-statement or direct-invocation queue driver for agile-workflow. Use when a harness goal or user request says to run autopilot, drain ready work, finish an epic, continue through .work/active/, or make autonomous progress on the substrate. Reads .work/active/, picks ready items by depends_on and

• board

  Launch and open the agile-workflow interactive substrate board for a project. Use when the user asks to open, view, serve, inspect, or launch the .work board, substrate board, kanban board, dependency board, or `work-view board`. Requires an existing agile-workflow `.work/` substrate, a compiled boa

• bold-refactor

  Find beautiful code abstractions and cross-cutting simplifications. Applies conceptual lenses (elimination, unification, inversion, algebraic, declarative, domain crystallization) to surface bold architectural reconceptions, then produces a refactor EPIC with child features tagged [refactor] and dec

• bug-scan

  Deep multi-angle correctness bug hunt. Use when the user asks to "scan for bugs", "bug hunt", "deep bug audit", "find hidden bugs", "find race conditions", or audit lurking correctness issues. Fans parallel scanner agents across relevant domains such as concurrency, async, state, resource leaks, tim

• convert

  Bootstrap or sync the agile-workflow substrate. Auto-detects repo state: bootstrap creates .work/, CONVENTIONS.md, the canonical AGENTS.md section, Claude compatibility, work-view, and migrated items; sync refreshes plugin-owned artifacts plus optional skill catalog mirrors while preserving user-own

• deep-code-scan

  Multi-lane, decomposition-first codebase scan campaign for agile-workflow. Use when the user asks for a deep code scan, comprehensive audit, whole-repo issue hunt, or organized fix plan that spans multiple lanes such as correctness, tests, performance, security, quality, structure, or architecture.

• e2e-test-design

  ALWAYS invoke this skill when the user asks to design e2e tests, audit or bootstrap the e2e program, or work on a [e2e-test]/[testing] feature at stage:drafting. Designs service-level-mocked e2e coverage, writes the design into the feature body, spawns child stories with depends_on chains, and advan

• epic-design

  ALWAYS invoke this skill when the user asks to design, decompose, or pick up an epic at stage:drafting. Reads the epic, foundation docs, and codebase; identifies child feature arcs; writes feature files with parent and depends_on metadata; updates the epic body with the realized decomposition; and a

• epicize

  Decompose foundation docs into multiple epics seeded in .work/active/epics/ with declared dependencies. Reads VISION.md, SPEC.md, ARCHITECTURE.md, identifies capability arcs, proposes an epic decomposition with depends_on chains, and writes the epic files at stage:drafting after user confirmation. U

• feature-design

  ALWAYS invoke when the user asks to design or flesh out a feature at stage:drafting; do not write design prose inline. Designs the feature inside its agile-workflow item body, grounded in foundation docs and code, then spawns child stories with depends_on chains and advances drafting to implementing

• fix

  ALWAYS invoke this skill when the user asks to fix a specific verified bug — do not just edit code inline. Diagnoses and repairs the bug as a focused substrate story: reproduces it, identifies the root cause, writes a failing test, applies the minimal fix, verifies it, and runs the bounded standalon

• gate-cruft

  Cruft gate focused on release-bound items that may follow relevant evidence into adjacent or system-wide code. Finds dead code, stale comments, low-value tests and checks, compatibility shims, defensive bloat, and over-abstraction, including whole systems that may no longer earn their cost. Delegate

• gate-docs

  Documentation gate that enforces the rolling-foundation principle. Delegates the full drift detection to a deep documentation scanner agent which scans the bundle's changes for foundation-doc drift (false, stale, or contradictory assertions—not missing coverage), changelog gaps, README staleness, an

• gate-patterns

  Patterns gate that scans the bundle's changes for reusable code structures. Delegates the full discovery to a deep pattern scanner agent which identifies recurring shapes (3+ occurrences) introduced or revealed by the bundle, names them, documents them with concrete file:line examples, and returns p

• gate-refactor

  Refactor gate that discovers scan-rule libraries declared in the host project (default roots: {project}/.agents/skills/scan-*/SKILL.md and {project}/.claude/skills/scan-*/SKILL.md; configurable via CONVENTIONS.md: gate_refactor_scan_library_roots), loads every discovered library, checks the release

• gate-security

  Security gate that scans items bound to a release and produces items as findings. Delegates the full audit to a deep security scanner agent which discovers stack, picks relevant security domains (auth, injection, secrets, deps, API, infra, crypto, data protection, error handling), audits the bundle'

• gate-tests

  Test-quality gate focused on release-bound items that may follow relevant evidence into adjacent interfaces and test systems. Derives useful coverage from contracts, risk, and bug history—not line coverage—and identifies both valuable gaps and low-value tests worth removing. Delegates the analysis t

• groom

  Backlog hygiene sweep for the agile-workflow substrate. Use when the user asks to groom the backlog, audit backlog hygiene, find stale/dead/duplicate/superseded backlog items, or clean up .work/backlog/. Triggers on "groom the backlog", "backlog hygiene", "find stale items", "what's dead in the back

• ideate

  Interactive project definition workshop for agile-workflow. Explores an idea through discovery, refinement, and definitions phases, then produces tailored foundation documents (VISION.md, SPEC.md, ARCHITECTURE.md, and domain-specific docs) that encode the rolling-foundation principle from day one. U

• implement-orchestrator

  ALWAYS invoke when the user asks to implement substrate items, work through stage:implementing items, drain the queue, or implement a feature or epic scope. Coordinates implementation from the unified dependency graph, uses one feature-owning worker as the baseline, bundles related features or split

• implement

  ALWAYS invoke this skill when the user explicitly asks to implement a substrate item inline, when the work is cohesive enough for one owner, or when the deliverable is no-code prose (a [prose] item of any size that needs no coordination). Inline implementation of an item at stage:implementing. Reads

• park

  ALWAYS invoke this skill when the user wants to capture an idea for later without derailing current work — do not start working on the parked idea inline. Captures short ideas, richer context notes, or roadmap-style multi-arc thoughts into the agile-workflow backlog under .work/backlog/ with minimal

• perf-design

  ALWAYS invoke when the user asks to profile performance, find bottlenecks, optimize code, make something faster, or design a [perf]-tagged feature; do not optimize inline. Discovery mode profiles likely hot paths and emits substrate items per bottleneck. Per-feature mode designs an existing stage:dr

• perf-scout

  Cross-domain performance *idea* generator — a speculative brainstorm engine, not a profiler. Use when the user asks for performance ideas, optimization angles, "how could this be faster", "what would a game engine / database / GPU do here", a perf brainstorm, "ways to speed this up", or a broad swee

• principles

  agile-workflow principles — code-design (clear boundaries, proportional rigor, code economy, useful tests, continuous simplification, and compatibility only for verified external consumers) and substrate-execution (Item-IS-the-Work, Rolling-Foundation, Late-Binding). Auto-loads when designing module

• prose-author

  ALWAYS invoke this skill when picking up a feature tagged [prose] at stage:drafting — a no-code-surface deliverable (docs, conventions, rules, research prose, copy, config-as-prose) whose design and implementation collapse into a single inline authoring act. Confirms the brief is a sufficient spec,

• refactor-conventions-creator

  Create or update a project-specific refactor-conventions catalog for agile-workflow. Explores the repo, researches stack-specific best practices, interviews the user about stylistic preferences and structural refactor preferences, writes concise style rules into the canonical AGENTS.md, writes detai

• refactor-design

  ALWAYS invoke this skill when the user asks to scan for refactor opportunities, plan a refactor, or design a [refactor]-tagged feature. Discovery mode scans code smells, separates pure refactors from behavior changes, and emits substrate items. Per-feature mode plans an existing [refactor] feature a

• release-deploy

  Cut a release in the agile-workflow substrate. Interactively binds items to a version, advances the release stage from planned to quality-gate, runs all configured gates in CONVENTIONS.md order (default: security, tests, cruft, docs, patterns), waits until all bound items + gate-produced items reach

• research

  ALWAYS invoke this skill when the user asks to research a library, API, SDK, or technology choice — do not just web-search and summarize inline. Researches external libraries, APIs, SDKs, and patterns to inform design and implementation. Investigates options, evaluates trade-offs against project nee

• review

  ALWAYS invoke this skill when the user asks to review a substrate feature or standalone story, an eligible item is at stage:review, or the user says "review this". Routes by item scope: child stories close on verification without review, standalone stories get a bounded inline pass, features get int

• scope

  ALWAYS invoke this skill when the user asks to scope, promote, formalize, cluster, or track new work — do not start drafting items inline. Promotes ideas from .work/backlog/ or fresh user requests into the active tier as epics, features, or stories with declared dependencies. Use when scoping new wo

Hooks (4)

• SessionStart

  PYTHONDONTWRITEBYTECODE=1 python3 "${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/hooks/scripts/prompt-context.py"

• UserPromptSubmit

  PYTHONDONTWRITEBYTECODE=1 python3 "${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/hooks/scripts/prompt-context.py"

• PostCompact

  PYTHONDONTWRITEBYTECODE=1 python3 "${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/hooks/scripts/prompt-context.py"

• PostToolUse

  PYTHONDONTWRITEBYTECODE=1 python3 "${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/hooks/scripts/substrate-maintainer.py"

Similar plugins