su-approve

Log explicit approvals for review items with system-level logging.

17|2|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/SeemSeam/agent-roles-spec --skill su-approve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: su-approve
Source: https://github.com/SeemSeam/agent-roles-spec/tree/main/roles/su-ccb/skills/su-approve
Command: npx skills add https://github.com/SeemSeam/agent-roles-spec --skill su-approve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a way to document user approvals for review items, such as drafts or risk matters, streamlining the approval process and ensuring clear documentation of decisions.

Core Features & Use Cases

  • Explicit Approval Recording: Documents user approvals for review items like drafts or risk matters.
  • Scalable Use: Can serve multiple nodes such as requirement analysis, technical design, task breakdown, and risk archiving.
  • Use Case: For a project manager to record explicit approval for a requirement review or a task breakdown, the 'su-approve' skill can be used to log the decision in the system.

Quick Start

To record approval for a requirement, use the command: `/ccb:su-approve --payload {"subject":"requirement","requirement_id":"<id>","action":"breakdown_draft_approve","expected_hash":"<hash>","reviewer_note":"User approval for the current draft."}

Frequently Asked Questions about su-approve

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

FAQPage Schema
How do I record explicit approval for a requirement review or risk matter?

To record explicit approval for a requirement review or risk matter, use a command-based logging skill to document user approvals for review items like drafts, ensuring clear decision documentation for administrative workflows.

What is the best way to document approval decisions for project management drafts?

The best way to document approval decisions for project management drafts is to use a review logging mechanism that utilizes system-level logging and approval transition logic to explicitly record user approvals.

Can I use approval recording for different project nodes like task breakdown and technical design?

Yes, approval recording is scalable and can serve multiple project nodes such as requirement analysis, technical design, task breakdown, and risk archiving to document explicit user approvals across various administrative workflows.

When do I need to log explicit approvals for risk management issues?

You need to log explicit approvals for risk management issues when your administrative workflows require formal approval tracking and clear documentation of decisions for risk matters or drafts.

Does approval transition logic work without additional dependencies?

Yes, the approval transition logic and system-level logging operate without additional dependencies, allowing you to document user approvals for review items directly within your project management environment.