structured-autonomy-plan

Name: structured-autonomy-plan
Availability: InStock
Author: yiwei79

Convert architect briefs into deterministic task plans with test strategies and validation gates.

1|Updated Apr 3, 2026

Search Tags:#automation #dependencies #agent workflow #test strategy #decomposition #task planning #validation gates

Ready to run

npx skills add https://github.com/yiwei79/root-azoth --skill structured-autonomy-plan-yiwei79

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: structured-autonomy-plan
Source: https://github.com/yiwei79/root-azoth/tree/main/.opencode/skills/structured-autonomy-plan
Command: npx skills add https://github.com/yiwei79/root-azoth --skill structured-autonomy-plan-yiwei79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fuzzy goals and design briefs often stall at the implementation stage because no one has broken them into concrete, verifiable tasks. This Skill turns an approved architect brief into a deterministic plan that any agent or future session can execute without clarification. ## Core Features & Use Cases - Task Decomposition: Breaks a goal into atomic, bounded tasks with explicit files, dependencies, and validation criteria. - Mandatory Test Strategy: Requires unit, integration, and acceptance criteria as part of every plan, not as an afterthought. - Risk and Entropy Estimation: Captures risks with mitigations and estimates change scope as GREEN, YELLOW, or RED zones. - Use Case: After an architect approves a design for a new monitoring feature, use this Skill to produce a sequenced task table with dependencies and validation steps that a builder agent can execute cold-start. ## Quick Start Ask the agent to convert the approved design brief into a structured autonomy plan with tasks, dependencies, and a test strategy.

Frequently Asked Questions about structured-autonomy-plan

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

FAQPage Schema

How do I turn a design brief into an executable task plan?▼

Restate the goal in one sentence, decompose it into atomic tasks with explicit files and validation criteria, then sequence tasks by declared dependencies. Finish with a mandatory test strategy covering unit, integration, and acceptance criteria.

What makes a task plan executable by another agent?▼

Each task must be completable in isolation, verifiable with a clear done signal, and bounded in scope. Dependencies must be explicit via depends_on fields, and the plan must include enough detail for cold-start execution without clarification.

When should I use a structured plan instead of implementing directly?▼

Use it after architect approval, for work requiring more than three discrete changes, for cross-agent handoffs, or for test-driven work. Single-step changes do not need a formal plan.

What are common task planning anti-patterns to avoid?▼

Avoid vague tasks like implement the feature, missing test strategies, implicit dependencies, and unbounded tasks touching more than five files. Each task needs explicit files, validation, and declared dependencies.

How does the plan estimate change risk before execution?▼

The plan includes an entropy estimate counting files to create and modify, classified into GREEN, YELLOW, or RED zones. Risks are listed with mitigations and severity ratings so reviewers can gate execution.