wusanto

Enforce verification gates and mission-based contracts for AI-generated work.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/fagemx/wusanto --skill wusanto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wusanto
Source: https://github.com/fagemx/wusanto/tree/main/skills/wusanto
Command: npx skills add https://github.com/fagemx/wusanto --skill wusanto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the accountability gap in AI-assisted development by providing a rigorous acceptance layer that ensures AI-generated work meets specific, verifiable criteria before it is considered complete.

Core Features & Use Cases

  • Mission Verification: Executes declared commands to validate that AI output satisfies defined goals, constraints, and stop conditions.
  • WorkUnit Contract Enforcement: Manages the lifecycle of coding missions through structured STEP.md contracts.
  • Use Case: Use this when you need to hand off AI-generated code to a client or auditor and must prove that the work has passed all required technical gates and quality checks.

Quick Start

Ask the agent to run the mission status command to inspect the current work unit and verify the active mission requirements.

Frequently Asked Questions about wusanto

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify AI-generated code meets acceptance criteria before delivery?

Verify AI-generated code by enforcing verification gates and mission-based contracts. This ensures outputs satisfy predefined technical constraints and success criteria before being considered complete.

What is a mission-based contract for AI coding governance?

A mission-based contract manages the lifecycle of coding missions through structured STEP.md files. It defines specific goals, constraints, and stop conditions to enforce quality assurance and accountability.

How do I enforce explicit operator confirmation for AI task outputs?

Enforce explicit operator confirmation by requiring manual approval for all mission-critical commands. This acceptance layer ensures accountability by validating AI work against predefined technical constraints before finalizing artifacts.

Can I use this acceptance layer for client handoffs and code audits?

Use this acceptance layer for client handoffs and code audits to prove AI-generated work has passed required technical gates. It provides artifact recording and systematic review against defined quality constraints.

What are the limitations of verifying AI work with mission contracts?

Verifying AI work with mission contracts requires predefined success criteria and explicit operator confirmation for critical commands. It cannot validate outputs if technical constraints are not declared upfront in the STEP.md contract.