execute

Orchestrate end-to-end software implementation for Linear tickets or ad-hoc tasks.

Updated Feb 24, 2021
One-click install
npx skills add https://github.com/roderik/roderik.github.io --skill execute-roderik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute
Source: https://github.com/roderik/roderik.github.io/tree/main/.agents/skills/execute
Command: npx skills add https://github.com/roderik/roderik.github.io --skill execute-roderik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates end-to-end software implementation work for Linear tickets or ad-hoc tasks, handling state routing, a persistent workpad, planning, tracer bullets, TDD, self-verification, and state transitions.

Core Features & Use Cases

  • Status-aware routing and workpad-based continuity across multi-session execution.
  • Delegation to planner and verifier sub-skills, enabling autonomous orchestration from intake to review.
  • Tracer-bullet-first approach combined with TDD-driven implementation and CI verification.
  • Supports autonomous mode via ralph.sh with workpad as the single source of truth and explicit completion signals.

Quick Start

Start an end-to-end ticket with ID PRD-xxx and let Execute orchestrate planning, implementation, and verification toward a ready-to-review PR.

Frequently Asked Questions about execute

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

FAQPage Schema
How do I orchestrate end-to-end implementation for Linear tickets?

End-to-end implementation for Linear tickets is orchestrated by managing state routing, persistent workpads, plan generation, CI verification, and PR transitions autonomously from intake to review.

What is a tracer-bullet-first approach combined with TDD-driven implementation?

The tracer-bullet-first approach establishes an end-to-end functional skeleton early, while TDD-driven implementation incrementally builds features through automated verification and CI checks.

How does workpad-based continuity handle multi-session software development tasks?

Workpad-based continuity maintains a persistent state record across multi-session execution, enabling autonomous operation and seamless resumption of stand-alone development tasks or Linear workflows.

Can I use autonomous mode with ralph.sh for ad-hoc development tasks?

Autonomous mode via ralph.sh supports ad-hoc development tasks by using the workpad as the single source of truth and issuing explicit completion signals when implementation and verification finish.

Does end-to-end implementation orchestration require manual CI verification and PR state transitions?

End-to-end implementation orchestration automates CI verification and PR state transitions, delegating planning and verification to sub-skills to reduce manual intervention during software execution.