draft / task

Draft task artefacts and entity-merge approval cards from action metadata.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Collectively-Gary/GaryOS --skill draft-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft / task
Source: https://github.com/Collectively-Gary/GaryOS/tree/main/data/skills/draft/task
Command: npx skills add https://github.com/Collectively-Gary/GaryOS --skill draft-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It drafts the operational artefact for playbook task actions, including a safe operator-facing path for entity-merge tasks, preventing silent misrouting and enforcing input validity before approval.

Core Features & Use Cases

  • Generic task drafting: Creates a concrete task artefact (for short playbooks) from the action’s index.md, context_refs, and signals/*, and records the drafting judgement in the standard draft trail shape.
  • Entity-merge draft card: Composes the approval-gate content for task_variant: entity-merge, validating required inputs (merge_winner, merge_loser) and domain constraints (path shapes, tombstone rules, and chain-depth cap) before producing the operator card.
  • Malformation safety: Treats unknown task_variant values as stuck (no automatic fallback to default) and refuses malformed entity-merge requests with precise awaiting_operator diagnostics.

Quick Start

Use the draft / task skill to draft a task artefact or generate the entity-merge approval card for an action whose /data/actions/<id>/index.md sets the appropriate task_variant and required frontmatter.

Frequently Asked Questions about draft / task

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

FAQPage Schema
How do I generate an approval-gate card for an entity-merge task?

Entity-merge drafting validates merge inputs like merge_winner and merge_loser against domain constraints such as path shapes and chain-depth caps before composing the operator-ready approval-gate card.

How do I draft a task artefact from playbook action files and signals?

Draft a task artefact by loading deterministic context from the action index.md, context_refs, and signals directories, then recording the drafting judgement in the standard trail shape.

What happens when an unknown task_variant value is encountered during task drafting?

Malformed discriminators and unknown task_variant values are treated as stuck during task drafting, refusing automatic fallback to default and preventing silent misrouting of the operational artefact.

How does entity-merge drafting handle unsafe merge graphs or malformed requests?

Malformed entity-merge requests are refused with precise awaiting_operator diagnostics, enforcing input validity and providing defensive handling for unsafe merge graphs without fallback.

Do I need specific filesystem contracts to draft task actions and write action trails?

Drafting task actions requires the /data filesystem contracts to load deterministic context, write stage-accurate trails, and resolve context_refs for short playbook task workflows.

What is the best way to validate merge inputs before composing an operator card?

Validate merge inputs by checking required fields like merge_winner and merge_loser, enforcing tombstone rules and chain-depth caps, and refusing unsafe merge graphs before producing the operator card.