acquire

Name: acquire
Availability: InStock
Author: tesserine

Materialize a work-unit artifact from an open forge ticket.

Updated Mar 3, 2026

Search Tags:#materialize #work-unit #acquire #forge-ticket #read-ticket #take-workflow

Ready to run

npx skills add https://github.com/tesserine/groundwork --skill acquire

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acquire
Source: https://github.com/tesserine/groundwork/tree/main/skills/acquire
Command: npx skills add https://github.com/tesserine/groundwork --skill acquire

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Acquisition enables starting execution from an existing forge ticket by materializing a work-unit artifact when no artifact exists yet.

Core Features & Use Cases

Reads a ticket's content and materializes a corresponding work-unit artifact that the take protocol can consume.
Maintains a one-way relationship where the ticket remains the planning home and the artifact is the execution snapshot.
Handles validation, returning a work-unit-quality defect if the ticket lacks usable acceptance criteria or is not open.

Quick Start

Acquire the work-unit artifact from the given open ticket and pass it to your take workflow.

Frequently Asked Questions about acquire

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

FAQPage Schema

How do I materialize a work-unit artifact from an existing forge ticket?▼

You can materialize a work-unit artifact by reading the ticket content and validating that the ticket is open. The acquire workflow then produces an artifact with a stable instance_id and verbatim handle for the take protocol to consume.

What happens if I try to acquire a work-unit from a closed forge ticket?▼

Acquiring a work-unit from a closed forge ticket fails validation. The workflow checks the ticket status and returns a work-unit-quality defect if the ticket is not open, halting the take workflow from proceeding.

Do I need an existing artifact to start the take workflow from a forge ticket?▼

No, the acquire workflow applies when no work-unit artifact exists yet. It bootstraps scoped work by reading the ticket content and materializing a new artifact so the take workflow can proceed.

Why does materializing a work-unit fail when acceptance criteria are missing?▼

Materializing a work-unit fails when acceptance criteria are missing because the workflow validates ticket content quality. If usable acceptance criteria are absent, it returns a work-unit-quality defect to ensure deterministic artifact derivation.

Can I use the acquire workflow to modify the original forge ticket content?▼

No, the acquire workflow maintains a one-way relationship where the ticket remains the planning home. The materialized artifact serves only as the execution snapshot and does not modify the original ticket.