swe-workflow

Orchestrate a five-stage software workflow from idea to shipped PR.

3|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/soulmachine/skills --skill swe-workflow-soulmachine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swe-workflow
Source: https://github.com/soulmachine/skills/tree/main/swe-workflow
Command: npx skills add https://github.com/soulmachine/skills --skill swe-workflow-soulmachine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires grill-with-docs, to-prd, to-issues, triage, planning-with-files, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the transition from an initial idea to a fully-fledged, shipped PR, addressing the complexities of software development workflows.

Core Features & Use Cases

  • Stage-Driven Workflow: Divides the process into clear stages: Setup, Clarification, Feature Enumeration, Spec, and Execution.
  • Artifact-Based Process: Each stage produces a human-readable markdown artifact to feed the next stage, ensuring transparency and auditability.
  • Triage for External Issues: Handles issues filed outside the main workflow, such as bug reports or feature requests, through a separate triage process.
  • Flexible Execution: Allows jumping into any stage of the workflow, making it adaptable to various entry points.
  • Security and Debugging: Ensures that the process is secure and transparent, with clear audit trails and the ability to debug at each step.

Quick Start

Start the swe-workflow by running /setup-matt-pocock-skills. This will set up the necessary configuration files and conventions for your repository.

Frequently Asked Questions about swe-workflow

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

FAQPage Schema
How do I manage the software development workflow from an initial idea to a shipped PR?

To manage the software development workflow from idea to shipped PR, use a stage-driven process that divides execution into Setup, Clarification, Feature Enumeration, Spec, and Execution. Each stage produces a markdown artifact to feed the next step.

What is the best way to track external bug reports and feature requests outside the main development flow?

The best way to track external bug reports and feature requests outside the main development flow is through a dedicated triage process. This handles issues filed externally and integrates them into the workflow without disrupting the primary pipeline.

Can I jump directly into the spec or execution stage if I already have a PRD?

Yes, you can jump directly into the spec or execution stage if you already have a PRD. The workflow supports flexible entry points, allowing you to adapt the process to various stages of your existing software development lifecycle.

How does an artifact-based software development process ensure transparency?

An artifact-based software development process ensures transparency by generating a human-readable markdown artifact at each stage. These artifacts feed the next stage, creating clear audit trails and enabling debugging at every step of the workflow.

Do I need to run a setup script before starting the feature enumeration and PRD creation stages?

Yes, you need to run a setup script before starting feature enumeration and PRD creation to initialize the necessary configuration files and conventions for your repository, ensuring the workflow stages execute securely and correctly.