apply

Executes approved features through implementation, verification, recovery, and truthful completion closeout.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/leonardoacosta/skills --skill apply-leonardoacosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apply
Source: https://github.com/leonardoacosta/skills/tree/main/leo-core/skills/apply
Command: npx skills add https://github.com/leonardoacosta/skills --skill apply-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams executing approved feature work often lose track of dependencies, claim completion prematurely, or corrupt shared resources when multiple sessions or harnesses run concurrently. This Skill enforces a disciplined lifecycle so every feature reaches a truthful terminal outcome backed by fresh verification and durable evidence. ## Core Features & Use Cases - Single and queued feature execution: Runs one approved feature or an ordered feature queue with dependency-aware scheduling and ready-set recomputation after every terminal event. - Concurrency and lease safety: Detects mutable-resource conflicts, serializes or isolates work, and coordinates cross-session ownership through a portable workflow lease with fencing and owner attribution. - Durable recovery and truthful closeout: Reconstructs interrupted work from repository evidence instead of chat memory, prevents duplicate external effects, and refuses premature completion claims. - Use Case: A queue of three features where B depends on A and C is independent: the Skill runs A first, keeps C eligible only when resources are isolated, and marks B blocked with its causal edge if A fails. ## Quick Start Use the apply skill to execute the approved feature proposal in this repository and carry it through verification, issue updates, and completion closeout.

Frequently Asked Questions about apply

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

FAQPage Schema
How do I execute an approved feature proposal safely?

Resolve the feature from authoritative proposal and issue state, confirm it is approved and dependency-ready, then claim it before editing. Run preflight checks, execute tasks in dependency order, verify with fresh tests, and close out with issue updates, archive, and persistence.

How do I run multiple features in parallel without conflicts?

Parallel execution is allowed only when dependencies are satisfied, ownership is disjoint, and mutable resources are isolated. Shared files, migrations, deployments, or credentials create concurrency conflicts that must be serialized or isolated through separate worktrees, databases, or environments.

When can a feature be marked as completed?

A feature is completed only when all tasks are implemented, fresh verification passes on the final bytes, issue state is updated, specifications are synchronized and archived, and required commits or pushes succeed. Passing targeted tests alone is never sufficient.

How do I resume interrupted work after losing chat context?

Reconstruct state from durable evidence such as proposals, tasks, issues, commits, working-tree state, and checkpoints rather than conversation summaries. Preserve verified partial progress and avoid repeating external effects unless evidence proves they did not complete.

What is a workflow lease and when is it needed?

A workflow lease coordinates ownership of mutable resources across sessions or harnesses through one shared authority with atomic acquisition, owner credentials, and monotonic fences. Use it whenever multiple participants can reach the same repositories, environments, or release surfaces.

What happens when a workflow lease expires during execution?

The expired owner becomes read-only and its stale fence cannot authorize mutation, release, commit, or deploy. A new holder takes over with a newer fence, and the old session must reconcile durable state before reacquiring the lease.