Skip to content
Back to skills

Lulu Exec

ASecurity

Use when: execute a delivered work order, task exec, coding TDD, action task, lulu-exec workflow, lulu-workflow lulu-exec, git worktree delivery.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 2, 2026
ai-agentspythongobashgit

Security analysis

A100/100

Pro scans all 20 files and shows the line behind each finding

Scanned October 5, 2026

npx -y skills add lulufoo/lulu-workflow --skill lulu-exec --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lulu Exec?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Lulu Exec
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lulufoo-lulu-exec/badge)](https://www.skillsdirectory.com/skills/lulufoo-lulu-exec)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: lulu-exec
description: >-
  Use when: execute a delivered work order, task exec, coding TDD, action task,
  lulu-exec workflow, lulu-workflow lulu-exec, git worktree delivery.
disable-model-invocation: true
---

# code-workflow

## Overview

Execute work-order tasks by `kind`. One task per sub-agent. `coding` runs in an isolated git worktree with TDD and a commit contract. `action` reaches a stated goal and records a receipt with evidence for every acceptance criterion; it runs in the project root unless the task names a worktree. Then a closing gate before delivery.

## Blocking policy

If the workflow cannot advance: **stop** (no retry, skip, or workaround), **report** the reason (stderr, exit code, or `TASK_FAILED`), and **wait** for user direction before continuing.

## Prerequisites

<HARD-GATE>
Do NOT proceed until you have read `../_runtime.md` and loaded:

- `$SKILL_ROOT`, `$WORKFLOW_DIR`, `$PLATFORM`, `$CACHE_DIR` from `## Platform Context`
- `$SKILL_DIR` = `$SKILL_ROOT/lulu-exec` (before Session Foundation)
- Feature identification logic from `## Session Foundation`
</HARD-GATE>

<HARD-GATE>
Do NOT proceed until you have read `../_subagent.md` 
</HARD-GATE>

## Commands

### `/lulu-exec [<cycle_id>]` — Entry point

Derive `$CYCLE_ID` via `_runtime.md` § Session Foundation, or use the explicit `<cycle_id>` argument if provided.

<HARD-GATE>
`$CYCLE_ID` must be resolved before proceeding. If it cannot be resolved → stop and ask the user to provide it.
</HARD-GATE>

Run entry recovery probe, branch on stdout JSON:

```bash
python3 "$SKILL_DIR/scripts/tc_session_control.py" \
  --cycle-dir "$CACHE_DIR/$CYCLE_ID" \
  check-recovery
```

- `recoverable: false` → ## Starting
- `recoverable: true`:
  - **Feature container** (`$CYCLE_TYPE == feature`): Announce `current_state`, `active_session`, and `current_task` (Executing only); auto-resume into ## `{resume_section}` — do not ask Yes/No.
  - **Topic container** (`$CYCLE_TYPE == topic`): Show the same fields; ask to resume. **Yes** → ## `{resume_section}` · **No** → ## Starting.

> lulu-exec is on the feature stage line only (`transition-table.json`); topic exception documents fallback if `/lulu-exec` is invoked on a topic cycle.

---

## State machine

Session states: `Starting` → `Preparing` → `Executing` → `Closing` → `Delivered`

Task phases live in the runner for `$CTX.kind`. Do not run the TDD chain for `action`.

---

## Starting

**Step 1: Run `start.py`**

```bash
python3 "$SKILL_DIR/scripts/tc_start.py" \
  --cycle-id "<cycle_id>"
```

> On non-zero exit: Apply § Blocking policy.

**Exit:** `start.py` succeeds → proceed to § Preparing.

---

## Preparing

Load `references/preparing.md`.

---

## Executing

Load `references/executing.md`.

---

## Closing

**Feature container** (`$CYCLE_TYPE == feature`): Auto-complete delivery — run `deliver` without user confirmation.

**Topic container** (`$CYCLE_TYPE == topic`): Wait for explicit user confirmation before running `deliver`.

Run:

```bash
python3 "$SKILL_DIR/scripts/tc_session_control.py" \
  --cycle-dir "$CACHE_DIR/$CYCLE_ID" \
  deliver
```

> Precondition: `current_state` must be Closing (enforced by script).
> On non-zero exit: Apply § Blocking policy.

**Exit:** deliver succeeds → § Delivered.

---

## Delivered

Session complete; stop.

---

Files in this skill

  • SKILL.md3.3 KB
  • action-runner/SKILL.md2.4 KB
  • config.json239 B
  • references/executing.md2.3 KB
  • references/preparing.md1 KB
  • scripts/tc_action_receipt_schema.py5 KB
  • scripts/tc_archive.py1.4 KB
  • scripts/tc_closing_checklist_schema.py2.7 KB
  • scripts/tc_code_log.py2 KB
  • scripts/tc_code_task_list.py3.5 KB
  • scripts/tc_commit_message.py513 B
  • scripts/tc_commit_ref_schema.py5.6 KB
  • scripts/tc_confirm_task_ready.py4.9 KB
  • scripts/tc_git_ops.py12.2 KB
  • scripts/tc_init.py531 B
  • scripts/tc_prepare.py17.2 KB
  • scripts/tc_repo_map_control.py4.3 KB
  • scripts/tc_repo_map_schema.py4 KB
  • scripts/tc_resolve_task_context.py7.9 KB
  • scripts/tc_run_test_suite.py6.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.