workflow-refine

Refine rough work requests into structured briefs for workflow-create.

3|3|Updated Aug 19, 2024
One-click install
npx skills add https://github.com/AMDResearch/dh_comms --skill workflow-refine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-refine
Source: https://github.com/AMDResearch/dh_comms/tree/main/.agents/skills/workflow-refine
Command: npx skills add https://github.com/AMDResearch/dh_comms --skill workflow-refine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn rough user input into an autonomy-ready brief. This helps teams transform vague, incomplete, or ambiguous work requests into concrete, actionable dossiers that can be fed into a workflow-creation process.

Core Features & Use Cases

  • Read user input or seed files to understand intent and scope.
  • Propose concrete workflow types and IDs, identify ambiguities, and draft a refined brief.
  • Ensure the final brief includes objective, acceptance criteria, scope, dependencies, and a plan for handoff to workflow-create.

Quick Start

Provide a rough work request or seed file; the skill will generate a structured, autonomous-ready brief for workflow-create.

Frequently Asked Questions about workflow-refine

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

FAQPage Schema
How do I turn vague project requirements into actionable briefs?

To turn vague project requirements into actionable briefs, provide your rough input or seed file. The skill parses the raw request to generate a structured brief containing an objective, acceptance criteria, scope, and non-goals for project execution.

What is a workflow seed file and how does it clarify project scope?

A workflow seed file is a rough input located at .agents/workflows/seeds/<name>.md. It clarifies project scope by providing initial context that the skill reads to identify intent, draft acceptance criteria, and flag overlaps with existing active workflows.

How do I generate acceptance criteria from a rough work request?

You generate acceptance criteria by submitting your rough work request to the skill. It analyzes the input, identifies ambiguities, proposes a workflow type and ID, and outputs a refined brief with concrete acceptance criteria and a failure policy.

Can I use this skill to detect overlapping tasks in project management?

Yes, you can detect overlapping tasks in project management using this skill. It draws context from active workflows and the project management index to flag potential overlaps with existing work when refining your brief.

Do I need a specific environment setup to refine work requests into autonomy-ready briefs?

You need access to the .agents directory structure to refine work requests. The skill reads seed files from .agents/workflows/seeds/, references .agents/pm/pm-index.md, and outputs the autonomy-ready brief for handoff to workflow-create.

What's the best way to define non-goals and dependencies for early-stage work requests?

The best way to define non-goals and dependencies for early-stage work requests is to input your raw request for processing. The skill explicitly drafts these boundaries within the refined brief, ensuring the workflow scope remains constrained and actionable.