clinearhub-workflow

Orchestrates the six-phase ClinearHub pipeline from spec creation through business validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Cianai/ClinearHub --skill clinearhub-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clinearhub-workflow
Source: https://github.com/Cianai/ClinearHub/tree/main/skills/clinearhub-workflow
Command: npx skills add https://github.com/Cianai/ClinearHub --skill clinearhub-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes and standardizes the ClinearHub six-phase PM workflow, enabling teams to discuss, implement, and validate complex pipelines with a consistent mental model and tooling context.

Core Features & Use Cases

  • Documents the six-phase pipeline (SPEC, TRIAGE, IMPLEMENT, MERGE, RECONCILE, REVIEW) and the roles of ChatPRD, GitHub Agents (gh-aw, Copilot), and GitHub Actions.
  • Clarifies label taxonomy, execution modes, duplicate detection, and cross-surface references to align team workflows across Linear, GitHub, and Cowork.
  • Serves as onboarding and reference material for sprint planning, incident response, and post-merge reconciliation in ClinearHub.

Quick Start

Describe a full six-phase flow from spec creation to business validation to illustrate the skill in action.

Frequently Asked Questions about clinearhub-workflow

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

FAQPage Schema
How do I automate a GitHub PM workflow from spec creation to business validation?

A six-phase PM workflow pipeline covers spec creation, triage, implementation, merge, reconciliation, and business validation. It standardizes complex pipelines using ChatPRD, Copilot, and GitHub Actions for consistent execution.

How do Copilot and GitHub Agents interact during issue triage and implementation?

Copilot and GitHub Agents interact during issue triage and implementation through agent dispatch and label taxonomy. This coordinates cross-surface references across Linear, GitHub, and Cowork to align team workflows.

What is the best way to standardize label taxonomy across Linear and GitHub?

Standardizing label taxonomy across Linear and GitHub requires a centralized workflow orchestration model. It clarifies execution modes, duplicate detection, and cross-surface references to align team workflows consistently.

Do I need GitHub Actions configured to run the six-phase PM pipeline?

You need GitHub Actions configured to automate the end-to-end PM workflow orchestration. The pipeline relies on Actions interacting with ChatPRD, gh-aw, and Copilot to execute spec creation through business validation.

How does post-merge reconciliation work in a GitHub workflow pipeline?

Post-merge reconciliation in a GitHub workflow pipeline occurs during the RECONCILE phase. It validates merged changes against business requirements before final review, ensuring cross-surface alignment across Linear and GitHub.

Can I use this workflow orchestration for sprint planning and incident response?

You can use this workflow orchestration for sprint planning and incident response. The six-phase pipeline serves as onboarding and reference material, standardizing execution modes and label taxonomy for complex PM scenarios.