feature-workflow

Plugin feature-workflow from marketplace schuettc-claude-code-plugins in schuettc/claude-code-plugins. Commands read from the repo's manifest — 1 month ago.

Skills (18)

• auditing-context

  Auto-load active audit context when working with audited code. Use when user is working on code that has an active audit session, discussing audit findings, or making changes related to a runtime audit. Silently loads audit session data to inform responses.

• checking-backlog

  Check project backlog when discussing feature ideas or priorities. Use when user mentions adding features, asks what's planned, discusses priorities, or proposes new functionality. Silently reads DASHBOARD.md to show relevant items and suggest /feature-capture for untracked ideas.

• feature-audit

  Runtime behavior auditing through systematic log injection. Use when user wants to understand what code is doing at runtime, debug complex flows, or audit a process.

• feature-autopilot

  End-to-end autopilot for driving a captured feature from idea.md through to merged PR. Chains feature-plan, feature-review-plan, feature-implement, feature-review-impl, and feature-ship with reviewer gates between phases. Auto-advances on PASS/CONDITIONAL PASS, pauses on FAIL. Use when the user says

• feature-capture

  Interactive workflow for adding items to the backlog. Use when user wants to add a new feature, track an idea, capture requirements, or mentions something that should be in the backlog.

• feature-deploy

  Coordinate a multi-repo deploy across a workspace's member repos in producer-first order. Use after a cross-repo epic's children have all merged and you need to release the members in dependency order (e.g. deploy the API producer before its consumers).

• feature-implement

  Execute a feature implementation plan from a clean context. Use when starting implementation after planning, or when resuming work on an in-progress feature. Reads plan.md and executes implementation steps.

• feature-init

  Initialize feature-workflow for a project, or refresh CI files with --update. Creates docs/features/, .feature-workflow.yml, and optional GitHub Actions review setup.

• feature-plan

  Start implementing a feature from the backlog with adaptive agent dispatch. Use when user wants to begin work on a backlog item, start implementation, or mentions a specific feature ID to work on.

• feature-review-impl

  Submit a feature implementation for external review via the existing draft PR, or respond to reviewer feedback on the code. Pushes implementation to the feature branch and updates the PR.

• feature-review-plan

  Submit a feature plan for external review via draft PR, or respond to reviewer feedback on the plan. Creates a feature branch, opens a draft PR containing the plan, and manages the review cycle.

• feature-search

  Search and filter features by state, assignee, priority, epic, dependency, type, or category. Use when the user wants to find features matching criteria — "what's paused", "what's court working on", "what's in the auth-overhaul epic", "what depends on X".

• feature-ship

  Complete a feature by writing shipped.md, committing to the feature branch, and merging the PR. Use when external reviews are done and the feature is ready to ship.

• feature-state

  Change a feature's state (active/paused/replaced/abandoned). Use when a feature needs to be paused while waiting on something, marked obsolete because another feature replaces it, or abandoned because it won't be pursued. Requires companion fields for non-active states.

• feature-status

  Display project status and backlog overview. Use when user asks about current status, what's in progress, what to work on next, or wants a summary of the backlog. Read-only skill that formats DASHBOARD.md into a clear dashboard view.

• feature-troubleshoot

  Systematic debugging mode with hypothesis-driven investigation. Use when user reports a bug, encounters an error, or needs help debugging a problem.

• guarding-scope

  Check if requested changes are within current feature scope. Use when user requests new functionality or changes during implementation that might be scope creep. Compares requests against feature requirements and suggests adding out-of-scope items to backlog.

• tracking-progress

  Update feature progress log and check off completed tasks. Use when user completes implementation tasks, makes commits, or indicates work is done. ASKS BEFORE MODIFYING files. Updates plan.md progress log section and implementation step checkboxes.

Subagents (12)

• api-designer

  Designs API contracts and data flow for features. Specializes in GraphQL schema design, Lambda function specifications, database structures, and authorization patterns. Creates clear API contracts between frontend and backend with complete error handling specifications.

• code-archaeologist

  Use PROACTIVELY when inheriting legacy codebases or before making changes to undocumented systems. This agent specializes exclusively in reverse-engineering complex code - tracing data flows, uncovering hidden dependencies, mapping system architecture, and identifying technical debt. Automatically g

• documentation-agent

  MUST BE USED whenever code is created or modified to maintain living documentation. This agent specializes exclusively in generating and maintaining technical documentation - creating API references, architecture diagrams, README files, and inline comments that stay synchronized with code. Automatic

• frontend-architect

  Designs React component architecture and state management for frontend features. Specializes in component hierarchy, props interfaces, state flow, and integration patterns. Creates clear component blueprints that are maintainable, testable, and performant.

• integration-designer

  Designs integration layer between frontend and backend. Specializes in GraphQL query usage, state synchronization, authorization flow, caching strategy, and error handling. Creates clear integration patterns that are secure, performant, and reliable.

• project-manager

  Use PROACTIVELY at the start of each sprint or product cycle to align technical work with business objectives. This agent specializes exclusively in product strategy and prioritization - creating roadmaps, defining acceptance criteria, analyzing market needs, and maximizing ROI. Automatically genera

• qa-engineer

  MUST BE USED before every release to ensure comprehensive quality validation and prevent defects from reaching production. This agent specializes exclusively in quality assurance - creating test plans, designing test cases, executing exploratory testing, and tracking quality metrics. Automatically g

• runtime-auditor

  Specialized agent for runtime behavior verification. Injects observational logs, captures execution data, and analyzes runtime behavior to verify code does what is expected. Use when you need evidence-based verification rather than static code inference.

• security-reviewer

  MUST BE USED before every deployment and pull request. This agent focuses solely on security vulnerability detection and remediation - scanning for OWASP Top 10, analyzing authentication/authorization, checking dependencies for CVEs, and validating data protection. Automatically blocks insecure code

• system-designer

  MUST BE USED when designing high-level system architecture for new projects or major system changes. This agent specializes exclusively in system design - creating component diagrams, defining service boundaries, designing data flows, and establishing integration patterns. Automatically creates syst

• test-generator

  MUST BE USED for all new feature development to enforce test-driven development (TDD). This agent specializes exclusively in writing comprehensive test suites BEFORE any implementation exists - generating unit tests, integration tests, edge cases, and error scenarios that define expected behavior. A

• ux-optimizer

  MUST BE USED when creating or modifying user-facing interfaces to ensure optimal user and developer experience. This agent specializes exclusively in UX optimization - analyzing user flows, improving interaction patterns, ensuring accessibility compliance, and enhancing developer ergonomics. Automat

Hooks (4)

• PreToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/pre_tool_use.py

• PreToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/pre_tool_use.py

• PostToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/post_tool_use.py

• PostToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/post_tool_use.py