skills.rest
BrunoAMSilva
BrunoAMSilvaCOMMUNITY
Explore all skills by this author →
GitHub

structured-autonomy-plan

Generate a commit-based PR workflow plan saved to plans/{feature-name}/plan.md.

Updated Apr 14, 2026
Search Tags:#planning#research#commits#autonomy#project-management#pull-request
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill structured-autonomy-plan-brunoamsilva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: structured-autonomy-plan
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/structured-autonomy-plan
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill structured-autonomy-plan-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design clear, executable development plans without writing code, by outlining research steps, commits, and PR-level changes for a single, unified plan.

Core Features & Use Cases

  • Structured autonomy planning that translates user requests into a sequence of commits and PR actions.
  • PR-oriented planning: each plan is designed as a single pull request with a dedicated branch.
  • Plan templating and scoping: outputs a file at plans/{feature-name}/plan.md detailing goals, steps, and tests.
  • Feedback loop: prompts for clarification and pauses for reviewer feedback before proceeding.
  • Reusable research framework: includes guidance to gather context, dependencies, and architectural considerations.

Quick Start

Provide a feature request and the agent will output a plan in plans/{feature-name}/plan.md with commit-by-commit steps.

Frequently Asked Questions about structured-autonomy-plan

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

FAQPage Schema
How do I plan software features as a sequence of commits for a pull request?▼

To structure software project plans without writing code, you map user requests into a commit-based PR workflow. This generates a plan file detailing goals, research steps, and PR-level changes for a single unified pull request.

How does a commit-based PR workflow map to project planning steps?▼

A commit-based PR workflow maps project planning by outlining research, dependencies, and architectural considerations before execution. It generates a templated plan file that breaks down feature execution into specific commits and review checkpoints.

What is the best way to scope a feature request into a single pull request?▼

The best way to scope a feature request into a single pull request is by generating a dedicated plan file under plans/{feature-name}/plan.md. This file scopes the feature by detailing goals, step-by-step commits, and tests.

Can I get reviewer feedback during automated project plan generation?▼

Yes, you can get reviewer feedback during automated project plan generation. The planning process includes a feedback loop that prompts for clarification and pauses for reviewer feedback before proceeding with the commit execution.

Do I need a YAML manifest to structure an autonomy plan for software projects?▼

Yes, you need a frontmatter-driven YAML manifest to structure an autonomy plan. The planning process satisfies requirements for this YAML manifest to generate a standardized plan template for your software projects.

Related Skills

Explore More Software Engineering Skills→
stijn-dejonghstijn-dejongh
1

spec-kitty.tasks-outline

Generate wps.yaml and tasks.md work package manifests from structured YAML.

Community
Advanced
kirvinkirvin

pr

Create a pull request for the current branch with an auto-generated title and body.

Community
Intermediate
michael-watsonmichael-watson
8

rpi-research

Analyze codebase architecture, dependencies, and constraints into a research document.

Community
Intermediate
Michae2xlMichae2xl

executing-plans

Execute detailed implementation plans with verification checkpoints and sub-skill integration.

Community
Advanced