prompt-generator

Generate structured task briefs with objectives, constraints, contracts, and DoD for multi-repo E2E orchestration.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/zero-rehq/opencode-kit --skill prompt-generator-zero-rehq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-generator
Source: https://github.com/zero-rehq/opencode-kit/tree/main/.opencode/skill/prompt-generator
Command: npx skills add https://github.com/zero-rehq/opencode-kit --skill prompt-generator-zero-rehq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a reliable bridge to generate long, structured prompts that guide an orchestrator in multi-repo E2E workflows. By normalizing inputs and standardizing the task brief, it reduces ambiguity and speeds up task initiation.

Core Features & Use Cases

  • Structured Task Briefs: Produces long, consistent briefs with objectives, constraints, scopes, and acceptance criteria.
  • Multi-Repo Coverage: Adapts prompts to multi-repo environments, contracts, and DoD requirements.
  • Integration-Ready: Outputs ready-to-use prompts for AI orchestrators and subagents, with references to required materials.

Quick Start

Use the Prompt Generator to create a long, structured task brief for a multi-repo E2E orchestration task, including objectives, constraints, contracts, and DoD.

Frequently Asked Questions about prompt-generator

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

FAQPage Schema
How do I generate consistent prompts for multi-repo E2E tasks?

To generate consistent prompts for multi-repo E2E tasks, use a prompt generator to normalize inputs and produce structured task briefs with objectives, constraints, contracts, and DoD requirements.

What is a structured task brief for E2E orchestration?

A structured task brief for E2E orchestration is a standardized prompt that enforces structure, defines acceptance criteria, and references DoD and E2E_TRACE materials to guide an orchestrator across several repos.

Can I use generated prompts to coordinate subagents across several repositories?

Yes, you can coordinate subagents across several repositories by generating integration-ready prompts that normalize inputs and reference required materials, contracts, and DoD for the orchestrator.

What's the best way to define scope and constraints for E2E workflow automation?

The best way to define scope and constraints for E2E workflow automation is to standardize the task brief, ensuring the generated prompt includes clear objectives, contracts, and DoD across all involved repos.

Do I need predefined DoD and E2E_TRACE references before generating E2E prompts?

Yes, predefined DoD and E2E_TRACE references are needed because the prompt generator enforces structure by normalizing inputs and directly referencing these materials in the output task brief.