sop-note

Capture process observations and file structured GitHub issues in magnum6actual/dev-sop.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/magnum6actual/dev-sop --skill sop-note
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sop-note
Source: https://github.com/magnum6actual/dev-sop/tree/main/common/skills/sop-note
Command: npx skills add https://github.com/magnum6actual/dev-sop --skill sop-note

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

File a process observation as a GitHub issue in the dev-sop repo when you spot an obvious process gap, failure, or missing guardrail during any build.

Core Features & Use Cases

  • Capture observations quickly and structure them into an actionable issue.
  • Enforce consistent triage and routing of SOP gaps to the right responder in magnum6actual/dev-sop.
  • Reuse a standardized template to ensure critical details are recorded for future fixes.

Quick Start

File a SOP note describing the observed gap in the build process.

Frequently Asked Questions about sop-note

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

FAQPage Schema
How do I file a process observation as a GitHub issue?

To file a process observation as a GitHub issue, use the /sop-note command to automatically capture context, classify severity, and draft a structured issue body for confirmation. It targets the magnum6actual/dev-sop repository to route process gaps to the right responder.

What is an SOP note for build process gaps?

An SOP note for build process gaps is a standardized GitHub issue that captures missing guardrails or failures observed during a build. It enforces consistent triage by using a reusable template to ensure critical details are recorded for future fixes.

How do I create standardized GitHub issues for workflow failures?

You create standardized GitHub issues for workflow failures by triggering the /sop-note command. It automatically extracts the build context, classifies the severity of the gap, and generates a formatted issue body before requesting your confirmation to submit it.

Can I use sop-note across any project to report missing guardrails?

Yes, you can use sop-note across any project or build to report missing guardrails. It applies universally to capture observed gaps and structure them into actionable issues, routing them directly to the magnum6actual/dev-sop repository.

Does the /sop-note command automatically classify issue severity?

Yes, the /sop-note command automatically classifies issue severity. It captures the build context, drafts the structured GitHub issue body with the classified severity level, and then requests your confirmation before actually creating the issue.