intelligent-prompt-generator

Generates context-aware Task and Phase briefs for OpenCode orchestrations.

Updated Jan 15, 2026

Search Tags:#orchestration #generate #briefs #task brief #consistency checking #phase brief #semantic understanding

Ready to run

npx skills add https://github.com/zero-rehq/opencode-kit --skill intelligent-prompt-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: intelligent-prompt-generator
Source: https://github.com/zero-rehq/opencode-kit/tree/main/.opencode/skill/intelligent-prompt-generator
Command: npx skills add https://github.com/zero-rehq/opencode-kit --skill intelligent-prompt-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of Task Briefs and Phase Briefs with semantic understanding and consistency checks, reducing manual drafting time and improving briefing quality across multi-repo workflows.

Core Features & Use Cases

3 Generation Modes: Task Brief, Phase Brief, and Gate Request generation to support builders, subagents, and reviewers.
Semantic Understanding: Extracts user intent, detects dependencies, and infers scope boundaries to ensure comprehensive briefs.
Consistency Checking: Validates that scope is coherent, Definition of Done is achievable, and flags missing information.
Context-Aware: Leverages supermemory and existing architecture patterns to tailor briefs to the project context.

Quick Start

Provide a user request like "Optimize this task brief for catalogos feature" and specify affected repos or architecture context to generate a ready-to-use Task Brief.

Frequently Asked Questions about intelligent-prompt-generator

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

FAQPage Schema

How do I generate task briefs for multi-repo workflows?▼

Task briefs for multi-repo workflows are generated by analyzing user requests, repository contexts, and architecture. The skill extracts user intent, detects dependencies, and infers scope boundaries to create ready-to-use briefs for builders and subagents.

What is a phase brief and when do I need it for software orchestration?▼

A phase brief defines orchestration steps for specific development phases, ensuring cross-repo contracts and Definition of Done criteria are met. It is needed when coordinating builders, subagents, and reviewers across multi-repo software engineering workflows.

How does consistency checking work for generated task briefs?▼

Consistency checking validates that the brief's scope is coherent and the Definition of Done is achievable. It flags missing information and cross-repo contract violations by leveraging semantic understanding of the project context.

Can I use existing architecture patterns to tailor briefs for my project?▼

Yes, briefs are tailored to your project by leveraging supermemory context and existing architecture patterns. This context-aware approach ensures generated briefs align with your established repository structures and orchestration roles.

Does this support generating gate requests for code reviewers?▼

Yes, gate request generation is supported as one of three core modes alongside task briefs and phase briefs. It produces context-aware prompts specifically designed to support the reviewer role in software orchestration workflows.