--- title: "engineering-workflow" description: "Engineering skills for issue backlog burn-down with runbook-driven validation and workspace setup, product mapping, build-failure diagnosis, complexity, consistency and conformance analysis, test design, scenario analysi" canonical: https://agentpluginsdirectory.com/plugins/engineering-workflow last-updated: 2026-10-08 --- # engineering-workflow Engineering skills for issue backlog burn-down with runbook-driven validation and workspace setup, product mapping, build-failure diagnosis, complexity, consistency and conformance analysis, test design, scenario analysis, technical debt reviews, and controlled technical writing. - Slug: engineering-workflow - Publisher: Steven Liekens - Repository: https://github.com/sliekens/agentic - Manifest: plugins/engineering-workflow/plugin.json - Version: 2.8.0 - License: MIT - Category (editorial): testing - Skills: 21 (analyze-complexity, blind-spot-coverage, cause-effect-graphing, combinatorial-testing, compound, cross-check, decision-tables, design-space-exploration, equivalence-partitioning-bva, fix-loop, flaky-build-investigation, fmea, operator-setup, product-map, realign, scenario-analysis, scenario-design, state-transition-testing, ste-writing, technical-debt-audit, workspace-setup) - MCP servers: 0 - Stars: 1 - Repository created: 2026-03-26 - Repository last pushed: 2026-09-29 - Publisher type: User - Listing: https://agentpluginsdirectory.com/plugins/engineering-workflow - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What engineering-workflow does, in the publisher's words This plugin provides engineering skills for product mapping, flaky-build diagnosis, operator setup, session compounding, consistency auditing, test design, scenario analysis, complexity analysis, and technical debt reviews. - Analyze Complexity: Analyze a code path, system, workflow, or architecture to separate inherent complexity imposed by requirements and external constraints from accidental complexity introduced by the current implementation, then define the invariants a simplification must preserve. Use when the user asks what complexity is necessary or unavoidable, asks for inherent vs. accidental complexity, says a pipeline or subsystem feels too complex, wants to understand why something cannot be simpler, or wants a complexity map before refactoring. Also use before a technical-debt audit when unavoidable constraints and removable implementation complexity are mixed together. Do not use for exploring competing greenfield designs (design-space-exploration) or for a pure structural-debt inventory that does not need an invariant boundary (technical-debt-audit). From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/sliekens/agentic/HEAD/plugins/engineering-workflow/README.md ## Skills - analyze-complexity: Analyze a code path, system, workflow, or architecture to separate inherent complexity imposed by requirements and external constraints from accidental complexity introduced by the current implementation, then define the invariants a simplification must preserve. Use when the user asks what complex… - blind-spot-coverage: Use this skill when the user wants to add test coverage targeting blind spots in a specific method, uncovered branches, edge cases, or unusual inputs. Activate on explicit requests to cover blind spots or when the user asks "what should I test here?" about a particular method. This is not about ac… - cause-effect-graphing: Build a directed graph connecting causes (inputs, preconditions) to effects (outputs, actions) through AND/OR/NOT logic nodes, then mechanically derive a decision table from it, for when conditional logic is too tangled to see clearly in prose or needs to be communicated visually to non-technical… - combinatorial-testing: Shrink an exponential combination space (feature flags, config options, API parameters) down to a minimal test matrix that still guarantees every pair of values is covered, pairwise/all-pairs testing, escalating to orthogonal arrays when 3-way interaction coverage is needed. Use eagerly whenever t… - compound: End-of-session hill climb on the instruction surface. Encodes this session's friction into AGENTS.md, skills, or project docs so the next session does not pay the same tax. - cross-check - decision-tables: Build a decision table that maps every meaningful combination of conditions to a specific outcome, and flags the combinations nobody has specified. Use eagerly whenever behavior is governed by combinations of independent yes/no conditions, authorization rules ("if role is admin AND resource is act… - design-space-exploration: Map the dimensions along which an architectural or design decision can vary, place known options in that space, and surface the unexplored regions and implicit assumptions before a decision gets locked in. Use eagerly when the user is deciding *how* to build something and multiple valid approaches… - equivalence-partitioning-bva: Turn a parameter's valid/invalid ranges into a systematic set of test cases by partitioning the input space into equivalence classes and probing the boundaries between them, where bugs disproportionately cluster. Use eagerly whenever the user needs test cases for numeric ranges (age, quantity, pric… - fix-loop - flaky-build-investigation: Diagnose intermittent build, test, packaging, or CI pipeline outcomes by comparing equivalent runs and correlating logs, configuration, code, environment, ordering, and timing. Use when a build or test sometimes fails, a rerun passes, behavior depends on runner or execution order, or the user asks… - fmea: Systematically enumerate failure modes for a system or process, score each by severity, likelihood, and detectability, and produce a prioritized risk register (Risk Priority Number = S × O × D). Use eagerly whenever the user asks "what could go wrong", wants a pre-launch risk review of a critical f… - operator-setup: Create or update a personal operator profile under ~/.agents/projects/: who the operator is, skill calibration, and collaboration preferences for this project. Only invoke when the user explicitly runs /operator-setup. Do not auto-trigger based on context. - product-map: Create or update a product map, feature map, or capability map from an existing implementation. Use when no map exists, when documenting what a program does, or after code changes add, alter, or remove capabilities that an existing map must reflect. Produces current-state documentation that plannin… - realign - scenario-analysis - scenario-design - state-transition-testing - ste-writing - technical-debt-audit - workspace-setup Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.