prometheus-planner

Interview users to generate self-contained implementation plans under .sisyphus/plans/.

Updated Jan 11, 2026

Search Tags:#planning #architecture #interview #plan-generation #oracle-consultation #execution-plans

Ready to run

npx skills add https://github.com/masrurimz/amp-sisyphus --skill prometheus-planner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prometheus-planner
Source: https://github.com/masrurimz/amp-sisyphus/tree/main/skills/prometheus
Command: npx skills add https://github.com/masrurimz/amp-sisyphus --skill prometheus-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams convert ambiguous requests into concrete, implementable plans without writing code, reducing miscommunication and accelerating architectural planning.

Core Features & Use Cases

Interview-first planning: Always interview before planning to elic it requirements, constraints, and success criteria.
Self-contained plans: Outputs ready-to-execute plans in .sisyphus/plans/ that another agent can follow without further questions.
Architecture guidance: Documents key decisions and trade-offs, optionally consulting the oracle for architecture guidance.
Clear handoff: Provides explicit acceptance criteria, risks, and dependencies to enable smooth handoffs to implementation teammates.

Quick Start

When a request arrives, begin with a brief interview to gather requirements, then generate a self-contained plan in .sisyphus/plans/ and present it for review.

Frequently Asked Questions about prometheus-planner

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

FAQPage Schema

How do I translate ambiguous system requests into executable architectural plans?▼

You translate ambiguous system requests into executable architectural plans by running an interview-first workflow to elicit requirements, then generating self-contained plan documents in .sisyphus/plans/ ready for implementation.

What is the best way to structure project breakdowns before writing any code?▼

The best way to structure project breakdowns before coding is to document key decisions, trade-offs, acceptance criteria, risks, and dependencies in a self-contained plan file.

How do I generate specifications that another agent can follow without further questions?▼

You generate specifications that another agent can follow without further questions by outputting self-contained plan documents under .sisyphus/plans/ that include explicit acceptance criteria and clear handoff details.

Can I use an oracle for architecture decisions during plan generation?▼

Yes, you can use an oracle for architecture decisions during plan generation to document key trade-offs and architectural guidance when consulting an available oracle.

Does the interview-first planning workflow require dependencies to execute?▼

No, the interview-first planning workflow requires no dependencies to execute, operating independently to elicit constraints and success criteria before generating plans.