se-work

Execute software engineering work plans with phase-structured workflows and quality gates.

Updated May 7, 2026
One-click install
npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: se-work
Source: https://github.com/simonwjackson/pi-software-engineering/tree/main/skills/se-work
Command: npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams orchestrate software engineering work by providing a repeatable workflow that coordinates planning, execution, testing, and shipping with quality gates.

Core Features & Use Cases

  • Phase-driven execution: Manage input triage, environment setup, and execution across multiple implementation units.
  • Quality-focused shipping: Integrates testing, linting, and review gates to ensure features ship correctly.
  • Plan-guided automation: Applies to work plans, plan documents, and iterative context switching during long-running projects.

Quick Start

Provide a work plan document or prompt and run the se-work execution loop to begin shipping features.

Frequently Asked Questions about se-work

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

FAQPage Schema
How do I automate software engineering work plans for shipping features?

To automate software engineering work plans, you provide a plan document to execute implementation units and testing steps across phase-structured workflows with built-in quality gates. This coordinates multi-unit execution and ensures features ship correctly.

What is phase-driven execution in software engineering?

Phase-driven execution is a workflow that manages input triage, environment setup, quick-start execution, testing, and post-ship validation. It coordinates implementation units sequentially to ensure software engineering tasks meet quality assurance standards.

Can I use plan-driven task execution across fresh-context iterations?

Yes, plan-driven task execution applies to fresh-context iterations during long-running projects. It coordinates execution across multiple implementation units while following existing project conventions for task tracking and review.

How do I integrate quality gates into a software engineering workflow?

You integrate quality gates by enforcing testing, linting, and review phases within the execution loop. This ensures features ship correctly by validating quality assurance criteria before completing post-ship validation.

Does this work with existing project conventions for testing and review?

Yes, the execution workflow follows existing project conventions for task tracking, testing, and review. It adapts to your established environment setup and quality assurance processes to ship features efficiently.