completion-core

Coordinate completion workflows for push, URL generation, and lifecycle events.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill completion-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: completion-core
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/completion-core
Command: npx skills add https://github.com/michael-conrad/.opencode --skill completion-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralize and automate the end-to-end completion workflow, including signaling completion, pushing branches, generating URLs, and appending lifecycle events to issue bodies.

Core Features & Use Cases

  • Centralized orchestration of completion signals and routing to verification gates and sub-agents
  • Idempotent operations with consistent executive summaries and status reporting
  • Use Case: Scale completion workflows across multiple issues and tasks with auditable lifecycle logs

Quick Start

Provide a task to generate a completion signal for an active issue and trigger the push and lifecycle update workflows.

Frequently Asked Questions about completion-core

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

FAQPage Schema
How do I automate task completion signals and lifecycle updates for active issues?

Automate task completion signals by orchestrating end-to-end workflows that push branches, generate URLs, and append lifecycle events to issue bodies. This provides centralized routing to verification gates and consistent status reporting.

What is the best way to ensure idempotent operations when managing task orchestration workflows?

Ensure idempotent operations in task orchestration by enforcing structured completion signals and verification gates. This approach prevents duplicate lifecycle updates and maintains consistent executive summaries across multiple issues.

How do verification gates work with completion routing for issue lifecycle events?

Verification gates work by intercepting completion routing signals to validate requirements before appending lifecycle events to issue bodies. This structured orchestration ensures only verified tasks trigger downstream updates.

Can I use centralized completion workflows to scale status reporting across multiple issues?

Yes, you can scale completion workflows across multiple issues using centralized orchestration. This approach applies structured routing and idempotent operations to generate auditable lifecycle logs and consistent executive summaries.

When do I need to append lifecycle events to issue bodies using task orchestration?

Append lifecycle events to issue bodies when your workflow requires auditable completion signals and structured status reporting. This is essential for scenarios demanding verification gates and consistent executive summaries after task completion.

Why are consistent executive summaries important for completion signal orchestration?

Consistent executive summaries are important because they provide standardized status reporting within completion signal orchestration. They ensure that idempotent operations yield auditable lifecycle logs across all routed verification gates.