chatha

Coordinate QA orchestration with stage gates and agent handovers.

Updated Nov 25, 2025
One-click install
npx skills add https://github.com/NikhilVijayakumar/Yantra --skill chatha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chatha
Source: https://github.com/NikhilVijayakumar/Yantra/tree/main/.agent/skills/chatha
Command: npx skills add https://github.com/NikhilVijayakumar/Yantra --skill chatha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tomli, and includes resources (resource) components.

What problem does it solve?

Orchestrates the governance of the Quality Assurance lifecycle by coordinating the four-stage orchestrator workflow and agent handovers, ensuring controlled, auditable activations.

Core Features & Use Cases

  • Stage-locked activation: Environmental Sovereignty, Doc-Architect blueprint creation, Test-Scaffolder test scaffolding, and Clean-Implementation with logging and strict quality gates.
  • State-aware execution: validates environment, root discovery from pyproject.toml, and blueprint-ID logging to maintain traceability even during resume or overrides.
  • Auto-failure safe handovers: recovers from missing artifacts, enforces zero-print policy, and prompts for remediation when gates fail.

Quick Start

Activate the System Manager with the command "System Manager, init chatha workflow" to begin Stage 0 environmental checks and trigger the full gating sequence.

Frequently Asked Questions about chatha

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

FAQPage Schema
How do I orchestrate QA handovers with stage gates for automated systems?▼

Orchestrate QA handovers by enforcing a four-stage gating sequence: environmental checks, blueprint creation, test scaffolding, and clean implementation. This coordinates agent handovers with state-aware execution and traceability logging for safe automation.

What is blueprint verification and how does it work in a QA lifecycle?▼

Blueprint verification is a stage-gate process that validates Doc-Architect blueprints before test scaffolding begins. It enforces Blueprint ID logging to maintain strict traceability across agent handovers during the QA orchestration workflow.

How do I enforce venv usage and root discovery via pyproject.toml for Python projects?▼

Enforce venv usage and root discovery by activating a system manager that validates the environment and locates the project root via pyproject.toml. This stage-locked activation ensures environmental sovereignty before downstream QA stages execute.

Can I use a zero-print policy with absolute imports and strict data models for QA gating?▼

Yes, a zero-print policy with absolute imports and strict data models is enforced during the clean implementation stage. This auto-failure safe handover recovers from missing artifacts and prompts remediation when quality gates fail.

What's the best way to recover from missing artifacts during agent handover stage gates?▼

Recover from missing artifacts using auto-failure safe handovers that detect absent files and prompt for remediation. This state-aware execution validates the environment and resumes the workflow while maintaining Blueprint ID logging traceability.

Do I need tomli to run chatha workflow stage gates?▼

Yes, tomli is required as a dependency to run chatha workflow stage gates. It supports the underlying system manager functionality needed for environment locking, root discovery, and strict quality assurance orchestration.