muc-opcua

Wrap core analysis with behavior-first vertical consistency checks.

Apply approved architecture refactors by updating plan and task artifacts directly.

Perform a framework-agnostic architecture review validating implementation against spec.md, plan.md, tasks.md, and the governance and architecture constitutions.

Perform an architecture-aware verification gate validating implementation against spec.md, plan.md, tasks.md, and the Architecture Constitution.

Run a single architecture workflow that prefers memory-first context and can incorporate security review when available.

Run implementation with memory context, then review the produced implementation against security and architecture constraints.

Orchestrate a governed planning workflow that coordinates flash-mem, Security Review, and Architecture Guard validation.

Generate or validate implementation tasks with memory context, security constraints, and architecture refactor/migration awareness.

Initialize or refine the project governance and architecture constitutions for Architecture Guard.

Convert architecture violations into non-blocking, structured refactor tasks.

Detect framework-agnostic architecture violations in plans, tasks, and implementation summaries.

Wrap core checklist generation with BDD, NFR, and Visual Fidelity readiness gate.

Wrap core clarification with spec-only ambiguity resolution.

Executes a single spec-kit phase by delegating its steps to specialized sub-agents sequentially and summarizing the outcome.

Wrap core constitution updates with change scope granularity and architecture SSOT governance.

Explain an implemented API or interface from repository facts for implementation understanding and defect localization.

Assess legacy codebase risks, reusable assets, constraints, and integration hazards.

Evaluate a scenario-specific technical decision for API, performance, migration, UX, or compatibility risks before formal planning.

Produce an evidence-backed feasibility study for a product or technical direction.

Derive a bounded-scope proof-of-concept and run it only when execution preconditions are met.

Build a technology selection matrix for candidate tools, libraries, platforms, or architectures.

Run a full project health diagnostic — checks structure, agents, features, scripts, extensions, and git status.

Run a full project health diagnostic — checks structure, agents, features, scripts, extensions, and git status.

Run agent-native implement orchestration or execute one worker handoff.

Ingest the reviewer's review-report.md and drive remediation, optionally using configured subagent routing for accepted fixes.

Initialize config or show status for the multi-model-review workflow, including spec-author, heavy-spec, implementation, review, subagent model routing, and optional Headroom-aware context compression.

Export a compact multi-model review package for the reviewer model, including spec-author, implementation, subagent routing, optional Headroom-aware context compression, and review model metadata.

Export a spec-authoring handoff prompt for the configured development spec model, model-specific options, and optional subagent task routing.

Wrap the core planning workflow with Phase 0 behavior projection and optional design artifacts.

Read-only pre-implementation briefing — surface what the roadmap expects for the spec about to be implemented (outcome, scope, governing decisions, dependencies) and flag pre-implementation drift.

Read-only post-implementation review — check the implemented spec against its roadmap entry's outcome and scope, classify any drift, and propose marking the entry verified.

Read-only reconciliation — detect drift between the roadmap ledger and the specs on disk (orphans, phantom entries, status drift, dependency contradictions, superseded ADRs).

Create or amend the project spec roadmap after the constitution — capturing spec-specific decisions, outcomes, constraints, and the intent of specs not yet written so they are not lost.

Generate a time budget showing estimated hours per phase, requirement, and risk buffer

Compare two specs or two versions of a spec to quantify scope differences

Detect scope creep by comparing current spec against its original version in git history

Estimate effort from spec complexity, requirement count, task phases, and technical decisions

Wrap core specification with spec-only requirement ownership.

Re-generate Squad agent definitions as your spec evolves

Initialize a Squad team from the current Speckit spec