kutusan

Orchestrate a five-stage pipeline to generate journal report sections from modular documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kutusan orchestrates a disciplined, multi-stage pipeline to generate a complete academic-style document from modular module data, ensuring traceable sourcing and minimized hallucinations.

Core Features & Use Cases

  • Orchestrates a 5-stage pipeline (Plan -> Analyze -> Augment -> Draft -> Review) for each paper section
  • Integrates data from Amsha, Yantra, Bodha layers and cross-module components to synthesize sections
  • Supports staged approvals and provenance tracking for high-assurance documentation generation.

Quick Start

Initiate the Kutusan 5-stage drafting workflow and provide per-section data sources to generate the final journal draft.

Frequently Asked Questions about kutusan

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

FAQPage Schema
How do I automate academic paper drafting from markdown documentation?▼

Automate academic paper drafting by orchestrating a five-stage pipeline that sequentially plans, analyzes, augments, drafts, and reviews each section from modular markdown sources to generate a complete journal report.

What is a multi-stage pipeline for generating scholarly papers?▼

A multi-stage pipeline for scholarly papers sequentially executes plan, analysis, augmentation, drafting, and review steps for each section, synthesizing modular documentation into a structured final journal report.

How do I ensure traceable sourcing and minimize hallucinations in academic writing?▼

Minimize hallucinations in academic writing by validating structured plans against repository documentation sources before drafting, enforcing provenance tracking throughout the staged section generation pipeline.

Do I need to provide execution results before generating the final journal report?▼

You must provide execution results at the specified markdown path within your repository's docs folder to finalize the output and complete the journal report generation workflow.

Can I use this workflow to orchestrate cross-module documentation into an 11-section paper?▼

You can orchestrate cross-module documentation into an 11-section paper by integrating data from architectural layers and applying the five-stage drafting workflow to synthesize the required sections.