Overview

Executing-plans locks the plan and drives it through cortex’s orchestration + verification stack, turning plan items into tracked tasks. It relies on /ctx:plan, Task view entries, and activated modes/rules to coordinate work, verify progress, and surface learnings. When done, it closes tasks and links learnings to the plan doc.

How This Skill Works

For each plan item, create or sync a corresponding Task view entry (T → A/E) and mirror the plan’s streams in category/workstream. Activate the required modes (3 view) and rules (4 view) to reflect the plan, then run workstream loops: pick a task, perform the work, and update status. Before moving to the next task, apply /ctx:verify checks (tests, lint, Supersaiyan visual) and finally update stakeholders with progress; when all tasks finish, retire tasks and capture retrospective learnings.

When to Use It

• You have a formal plan in /ctx:plan and need to convert it into actionable tasks in the Task view.
• Multiple streams or workstreams must be synchronized with mirroring plan streams in category/workstream.
• You require strict verification before progressing to the next task (tests, lint, visual checks).
• Stakeholders need consistent progress updates with summarized status and evidence.
• All tasks are complete and you want to capture retrospective learnings and link to the plan doc.

Quick Start

1. Step 1: Create/Sync Tasks from each plan item in the Task view and mirror plan streams.
2. Step 2: Activate required modes and rules to match the plan.
3. Step 3: Run workstream loops, perform work, use /ctx:verify before moving to the next task, then update stakeholders and close tasks when complete.

Best Practices

• Ensure /ctx:plan is present before starting.
• Mirror plan streams in task category and workstream for traceability.
• Regularly run workstream loops and promptly update task status.
• Apply /ctx:verify checks between tasks and attach evidence (screenshots, logs).
• Close tasks and record learnings in chat, linking to the plan doc after retrospective.

Example Use Cases

• Engineering sprint: Convert the sprint plan into Task view items, verify with tests, and report to stakeholders.
• Product launch: Align frontend, backend, QA streams with plan streams; run loops and verify before rollout.
• DevOps deployment: Translate deployment plan to tasks, run checks, and attach logs.
• Content release: Plan-to-task translation for editorial, design, and publishing streams with updates.
• Research data collection: Plan items turned into tasks with verification and retrospective.

Frequently Asked Questions