structured-autonomy-generate

Generates copy-paste ready implementation documentation from PR plan files.

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill structured-autonomy-generate-ultraviollettnympho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: structured-autonomy-generate
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/structured-autonomy-generate
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill structured-autonomy-generate-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a high-level PR plan into concrete, step-by-step implementation documentation with complete code is time-consuming and error-prone, often leaving developers with ambiguous instructions or placeholder code. ## Core Features & Use Cases - Plan Parsing: Reads a plan.md file from plans/{feature-name}/ and extracts the feature name, branch, and numbered implementation steps. - One-Time Codebase Research: Runs a single comprehensive research pass covering project structure, coding conventions, build commands, and official library documentation before generating output. - Complete Implementation Files: Produces an implementation.md with copy-paste ready code blocks, markdown checkboxes for every action, verification checklists, and mandatory stop-and-commit points between steps. - Use Case: A developer has an approved plan.md for a new feature and needs a full implementation guide with tested code, exact file paths, and per-step verification that another agent or teammate can execute without making decisions. ## Quick Start Ask the agent to read plans/my-feature/plan.md and generate the complete implementation documentation saved to plans/my-feature/implementation.md.

Frequently Asked Questions about structured-autonomy-generate

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

FAQPage Schema
How do I generate implementation documentation from a PR plan?

Place your plan in plans/{feature-name}/plan.md and invoke the generator. It parses the plan, runs one research pass over the codebase, then writes a complete implementation.md with code blocks, checkboxes, and verification steps.

What input format does the implementation plan generator require?

It requires a plan.md file located in plans/{feature-name}/ containing the feature name, target branch, and numbered implementation steps. The feature name determines the output folder for the generated implementation.md.

Does the generated implementation plan include actual code?

Yes, every step includes complete, copy-paste ready code blocks with exact file paths. The template explicitly forbids placeholders, TODO comments, and decide-for-yourself instructions.

How does the generator handle verification between implementation steps?

Each step ends with a verification checklist covering build errors and UI checks, followed by a mandatory STOP & COMMIT point. The agent must pause and wait for the user to test, stage, and commit before continuing.

What are the limitations of plan-based implementation generation?

The output quality depends entirely on the completeness of the input plan.md and the single research pass. It does not iterate on research mid-generation, so missing plan details can produce gaps in the documentation.