execute

Execute active plans and update tracked feature statuses in features.yaml.

1|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/masta-g3/rules --skill execute-masta-g3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute
Source: https://github.com/masta-g3/rules/tree/main/skills/execute
Command: npx skills add https://github.com/masta-g3/rules --skill execute-masta-g3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the execution of an active plan and coordinates progress across tracked features to reduce manual handoffs and ensure consistent state in planning repositories.

Core Features & Use Cases

  • End-to-end plan execution: Baseline verification, implementation, quality checks, and session termination.
  • Tracked feature management: Automatically updates statuses (e.g., in_progress, done) in response to plan progression and discovered work.
  • Guardrails and prompts: Enforces user consultation when blocked and surfaces a clear final status with PLAN COMPLETE or PENDING STEPS.

Quick Start

Run the active plan to implement all tasks and advance the tracked features accordingly.

Frequently Asked Questions about execute

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

FAQPage Schema
How do I automate active plan execution and update feature tracking?

Automate active plan execution by running phased steps that verify baselines, implement tasks, and update feature statuses. This coordinates progress across tracked features to reduce manual handoffs and ensures consistent state in planning repositories.

How does features.yaml tracking work during software development workflows?

Features.yaml tracking works by automatically updating feature statuses like in_progress and done in response to plan progression. This ensures tracked feature management stays synchronized as discovered work is implemented during delivery.

What is the difference between PLAN COMPLETE and PENDING STEPS statuses?

PLAN COMPLETE indicates all phased steps finished successfully and tracked features advanced to done. PENDING STEPS means the execution halted due to discovered work or blockers, requiring user consultation before advancing further.

Can I use this for end-to-end delivery from baseline verification to session termination?

Yes, it supports end-to-end plan execution covering baseline verification, implementation, quality checks, and session termination. This works for software development workflows relying on plans, features.yaml tracking, and ticketing to drive delivery.

What do I need to set up before running an active plan with features.yaml?

You need an active plan, a features.yaml tracking file, and a ticketing system to drive delivery. These planning repository components provide the baseline verification and tracked features required to execute phased steps and update statuses accurately.