god-agent-plan

Name: god-agent-plan
Availability: InStock
Author: fiatkongen

Orchestrate multi-phase planning workflows to generate specs, architecture, and implementation plans.

Updated Jan 15, 2026

Search Tags:#workflow #planning #architecture #documentation #codebase #spec #God-Agent

Ready to run

npx skills add https://github.com/fiatkongen/saurun-marketplace --skill god-agent-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: god-agent-plan
Source: https://github.com/fiatkongen/saurun-marketplace/tree/main/plugins/saurun/skills/god-agent-plan
Command: npx skills add https://github.com/fiatkongen/saurun-marketplace --skill god-agent-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates a structured, multi-phase planning workflow for God-Agent projects, integrating research, interviews, and external reviews to produce comprehensive artifacts.

Core Features & Use Cases

End-to-end planning workflow: coordinates research, interviews, and external reviews to generate specs, architecture, and implementation plans.
Artifact generation: outputs self-contained docs under _docs/specs, _docs/plans, and .god-agent directories for traceability and execution.
Guided collaboration: uses prompts and subagents to gather insights, validate decisions, and surface integration notes.

Quick Start

Run the god-agent-plan command with your initial brief, then follow the guided prompts to complete input validation, research decisions, interviews, spec synthesis, and artifact generation.

Frequently Asked Questions about god-agent-plan

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

FAQPage Schema

How do I plan architecture and specs for a complex codebase project?▼

To plan architecture and specs for a codebase, you can use a structured workflow that integrates research, interviews, and external reviews to generate comprehensive artifacts. This process enforces a standardized pipeline to produce self-contained docs for traceability.

What is the best way to coordinate UI and backend planning boundaries?▼

Coordinating UI and backend planning boundaries is best handled by a multi-phase workflow that analyzes input to synthesize specs, architecture, and implementation plans. It surfaces integration notes across design-system and codebase considerations to ensure alignment.

How do I generate traceable implementation plans from an initial brief?▼

Generating traceable implementation plans from an initial brief involves running a guided command that validates input, drives research decisions, and synthesizes specs. This outputs self-contained documents under designated directories for execution and traceability.

Can I use automated interviews to gather insights for software architecture decisions?▼

Yes, you can use guided prompts and subagents to conduct automated interviews that gather insights and validate decisions for software architecture. This collaborative approach ensures design and codebase considerations are thoroughly evaluated before artifact generation.

Do I need any specific dependencies to run a multi-phase project planning workflow?▼

No specific dependencies are required to run this multi-phase project planning workflow. The skill operates independently to orchestrate research, interviews, and external reviews, producing standardized architecture and spec artifacts directly in your project directories.

When should I avoid using a structured artifact pipeline for project planning?▼

You should avoid using a structured artifact pipeline for project planning when your project scope is too small to require formal specs, architecture documentation, or multi-phase interviews, as the overhead of generating traceable docs outweighs the benefits.