leader-signoff

Generate a signed leader signoff with score and verdict for mission accountability.

2|3|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/genesis-agents/GenesisPod --skill leader-signoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: leader-signoff
Source: https://github.com/genesis-agents/GenesisPod/tree/main/backend/src/modules/ai-app/playground/mission/skills/leader-signoff
Command: npx skills add https://github.com/genesis-agents/GenesisPod --skill leader-signoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill formalizes the final accountability gate by consolidating inputs and producing a single, signed or refused decision tied to the leader's prior M0/M1 choices.

Core Features & Use Cases

  • Independent leader score and verdict to certify mission outcomes.
  • Accountability notes referencing prior decisions for traceability.
  • Enforcement of sign/refuse rules with clear refusal reasons when necessary.
  • Suitable for missions requiring governance gates and post-mortem artifacts.

Quick Start

To use this skill at mission end, submit the leader's decision to generate a signed or refused signoff.

Frequently Asked Questions about leader-signoff

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

FAQPage Schema
What is a leader signoff in mission governance?

A leader signoff formalizes the final accountability gate for a mission, producing a signed or refused decision tied to prior M0/M1 choices. It certifies mission outcomes by issuing a formal verdict and score.

How do I enforce decision verification for postmortem accountability?

Decision verification for postmortem accountability is enforced by validating consistency between the leader's overall score and verdict. The system applies defined sign and refuse rules to ensure governance gate compliance.

Can I refuse a mission accountability signoff and provide a reason?

Yes, you can refuse a mission accountability signoff. The output schema includes an optional refusalReason field, allowing the leader to document exactly why the final governance gate was not approved.

What data is included in a formal leader signoff?

A formal leader signoff includes the leaderOverallScore, leaderVerdict, accountabilityNote, and a signed status. These fields consolidate inputs to trace the leader's final decision back to prior choices.

When do I need a final accountability gate for mission governance?

You need a final accountability gate for mission governance when a project requires a formal leader verdict and score. It is specifically suited for missions requiring governance gates and post-mortem artifacts.

How does the ReAct finalize wrapper deliver the accountability signoff?

The ReAct finalize wrapper delivers the accountability signoff by executing the formal decision process and outputting the validated schema. This ensures the leader's signed or refused verdict is structurally consistent.