triage-workflow

SOC II triage workflows automate the process of converting issues into Linear tickets, git branches, OpenSpec proposals, and traceable commits in a single orchestrated flow. This Skill uses linearis, OpenSpec, and GitHub CLI to enforce ticket prefixes, branch naming standards, and spec validation—turning manual triage into a CLI-driven, audit-ready pipeline.

Yes. This Skill creates Linear tickets via linearis CLI, then automatically generates git branches named after ticket identifiers. You can then generate OpenSpec proposals for spec-driven development, validate them, apply changes, commit with ticket prefixes, and optionally create PRs—all within a single triage workflow.

Enforce ticket prefixes in commits by integrating Linear ticket creation with branch management and OpenSpec proposals. This Skill orchestrates that integration: tickets drive branch names, branches structure commits, and OpenSpec proposals validate changes before they're applied and committed with traceable prefixes.

Yes. This Skill requires linearis for Linear ticket creation, OpenSpec for proposal generation and validation, and GitHub CLI for optional PR workflows. All three dependencies work together to create a complete SOC II compliant triage pipeline from issue to merged PR.

Spec-driven development using OpenSpec proposals creates an audit trail of design decisions before code changes. This Skill integrates proposals into the triage workflow: after ticket and branch creation, proposals are generated, validated by you, then applied—ensuring every change is documented and traceable for compliance.

Yes. This Skill enables subagent delegation to keep your main conversation context focused while triage orchestration runs independently. Tickets, branches, proposals, and commits proceed in the background, reducing conversation clutter while maintaining full traceability and SOC II audit requirements.