sisyphus-design

Produce structured design documents with decision logs and change summaries.

32|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/arkbriar/sisyphus-design --skill sisyphus-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sisyphus-design
Source: https://github.com/arkbriar/sisyphus-design/tree/main/codex
Command: npx skills add https://github.com/arkbriar/sisyphus-design --skill sisyphus-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Produces structured, high-quality design documents that capture decisions, trade-offs, and actionable implementation guidance so teams can move from requirement to implementation with minimal back-and-forth.

Core Features & Use Cases

  • Multi-phase methodology: Research, divergent approaches, interrogations, decision logs, drafting, automated evaluator loops, and human review touchpoints.
  • Decision-first output: Explicit Decision Log and critical-path focus that drives a directive design the consumer can implement.
  • Automated refinement: Spawned research and evaluator subagents plus convergence rules that iterate until the design stabilizes; writes the canonical design file to the project.

Quick Start

Invoke the skill with a concise design requirement like: /sisyphus-design Distributed task queue with at-least-once delivery, backed by PostgreSQL, implemented in Rust.

Frequently Asked Questions about sisyphus-design

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

FAQPage Schema
How do I write a production-ready architecture design document?

Produce a structured design document by applying a multi-phase methodology that includes research, divergent approaches, interrogations, and a decision log to capture trade-offs and actionable implementation guidance.

What is a decision log in system design and when do I need one?

A decision log in system design records explicit trade-offs and critical-path choices, and is needed when producing directive architecture proposals or component specifications to ensure teams move from requirement to implementation with minimal back-and-forth.

How do I structure a design doc for trade-off analysis?

Structure a design doc for trade-off analysis by incorporating multi-phase research, exploring divergent approaches, documenting decisions in a log, and applying automated evaluator loops to iterate until the system design stabilizes.

Can I automate the refinement of a component specification?

Yes, you can automate component specification refinement by spawning research and evaluator subagents that apply convergence rules, iterating through evaluator loops and human review touchpoints until the design stabilizes into a canonical file.

What is the best way to generate a protocol design from a requirement?

The best way to generate a protocol design from a requirement is to invoke an iterative design process that drafts the specification, applies automated refinement, and outputs a concrete design file and change summary.

Does this design process support human review touchpoints?

Yes, the design process supports human review touchpoints by integrating them into automated evaluator loops, ensuring that the final architecture proposal and decision log are validated before writing the canonical design file to the project.