Vague architecture leaves teams with incompatible interfaces and undocumented decisions. This skill structures architecture, decisions, contracts, and component designs for human review before specification.

Long coding projects lose context, decisions, and review evidence across sessions. Executor records initiative state and coordinates phase routing, task dispatch, and approval gates.

NestJS changes can introduce incompatible syntax, hidden side effects, and public API regressions. This skill guides repository inspection, focused implementation, and evidence-based verification.

Unclear responsibilities and unnecessary abstractions make NestJS code difficult to change and test. This skill guides evidence-based object design, pattern selection, and behavior-preserving refactoring.

Mixed changes and unclear publication requests can produce misleading commits or unintended remote updates. This skill guides verified Git changes and accurate messages within authorized scope.

NestJS runtime changes can create latency, security, and deployment failures when teams lack clear contracts and measurements. This skill guides component selection, bottleneck diagnosis, and reliable implementation using repository evidence and focused tests.

Source code alone cannot establish whether a NestJS feature satisfies its roadmap. This skill compares requirements with revision-specific evidence and reports completed work, gaps, legacy paths, bugs, and blockers.

NestJS repositories can hide boundary flaws and runtime risks that lint results alone cannot reveal. This skill combines local evidence collection and semantic review into one prioritized report.

Unclear module boundaries make NestJS changes harder to test and coordinate. This skill guides evidence-based architecture decisions, explicit ownership, and incremental boundary repairs.

Many application features need semantic judgments, but free-form model responses are difficult to combine reliably in code. TypeSafe helps developers design small typed judgments and compose them into routing, ranking, extraction, verification, and interactive workflows.

Trading ideas often lose context across tools and conversations. This skill stores validated thesis records, manages lifecycle changes, and produces reviews and postmortems.

Weekly charts can produce conflicting signals and vague forecasts. This skill structures chart evidence into trends, levels, patterns, and probability-weighted scenarios.

Manual trade decisions can bypass plans and risk controls. This skill checks local inputs and records a clear decision before broker entry.

Backtest results can hide overfitting, weak samples, and unrealistic execution assumptions. This skill applies structured scoring, stress tests, and bias checks.

Per-workspace environment recipes can fail because CLI selection and provider lifecycle details vary. This skill loads Orca guidance matched to the active version.

Linear ticket work can become inconsistent across issue updates, workflow transitions, and completion records. This skill uses Orca to guide ticket discovery, execution, and documented closure.

iOS testing often requires switching between agent tools, simulator controls, and evidence collection. This skill routes simulator interaction through Orca and loads guidance matched to the active CLI.

Teams often declare work complete without proving every requirement, path, review, and gap. This skill creates a traceable chain from intent to evidence and a defensible delivery decision.

Development teams can lose requirement evidence across planning, implementation, review, and release. This skill adds RVTF traceability while preserving Superpowers task boundaries and control.

OpenSpec tasks and archive states do not prove evidence-backed completion. This skill maps requirements, acceptance items, journeys, and gates into an auditable RVTF closure process.