input-template

Collect structured ISD planning inputs via YAML frontmatter and Markdown body.

33|10|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/orientpine/honeypot --skill input-template
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: input-template
Source: https://github.com/orientpine/honeypot/tree/main/plugins/isd-generator/skills/input-template
Command: npx skills add https://github.com/orientpine/honeypot --skill input-template

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ISD planning often requires assembling diverse inputs into a coherent plan. This template consolidates required fields for orchestrator-driven ISD plan generation, reducing setup time and ensuring consistency across chapters.

Core Features & Use Cases

  • Unified input schema for ideas, org info, technical focus, commercialization, and prior work to drive multi-chapter ISD plans.
  • Structured YAML frontmatter and rich Markdown body that the orchestrator consumes to generate sequential chapters.
  • Use Case: A research team seeds an ISD proposal template and generates Chapters 3, 1, 2, 4, and 5 in order via orchestrator.

Quick Start

Run the orchestrator-generator with this template to create the ISD plan chapters in order.

Frequently Asked Questions about input-template

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

FAQPage Schema
How do I structure inputs for orchestrator-based ISD plan generation?

ISD plan generation requires a unified input template combining YAML frontmatter with a rich Markdown body to drive multi-chapter document creation across idea, organization, and technology domains.

What is the best way to consolidate diverse research planning inputs into a coherent proposal?

Consolidating research planning inputs uses a structured template to unify diverse fields like commercialization and prior work into a single schema, ensuring consistency for downstream orchestrator consumption.

Can I use a Markdown template to generate sequential ISD plan chapters?

A Markdown template supports sequential ISD plan chapter generation when paired with an orchestrator, outputting ordered chapters like 3, 1, 2, 4, and 5 based on the structured input body.

Do I need YAML frontmatter to drive multi-chapter ISD document generation?

YAML frontmatter is required for multi-chapter ISD document generation, providing the essential name and description metadata fields that the orchestrator consumes to process the rich Markdown body.

What information should I include in an ISD planning input template?

An ISD planning input template should include structured information covering ideas, organization details, technical focus, commercialization strategies, and prior work to ensure comprehensive orchestrator-driven plan generation.

How does the orchestrator consume the input template to generate an ISD plan?

The orchestrator consumes the YAML frontmatter and rich Markdown body from the input template to automatically generate sequential ISD plan chapters, reducing manual setup time and ensuring structural consistency.