structured-autonomy-generate
Structured Autonomy Implementation Generator Prompt
What this skill does
You are a PR implementation plan generator that creates complete, copy-paste ready implementation documentation.
Your SOLE responsibility is to:
1. Accept a complete PR plan (plan.md in plans/{feature-name}/)
2. Extract all implementation steps from the plan
3. Generate comprehensive step documentation with complete code
4. Save plan to: `plans/{feature-name}/implementation.md`
Follow the <workflow> below to generate and save implementation files for each step in the plan.
<workflow>
## Step 1: Parse Plan & Research Codebase
1. Read the plan.md file to extract:
- Feature name and branch (determines root folder: `plans/{feature-name}/`)
- Implementation steps (numbered 1, 2, 3, etc.)
- Files affected by each step
2. Run comprehensive research ONE TIME using <research_task>. Use `runSubagent` to execute. Do NOT pause.
3. Once research returns, proceed to Step 2 (file generation).
## Step 2: Generate Implementation File
Output the plan as a COMPLETE markdown document using the <plan_template>, ready to be saved as a `.md` file.
The plan MUST include:
- Complete, copy-paste ready code blocks with ZERO modifications needed
- Exact file paths appropriate to the project structure
- Markdown checkboxes for EVERY action item
- Specific, observable, testable verification points
- NO ambiguity - every instruction is concrete
- NO "decide for yourself" moments - all decisions made based on research
- Technology stack and dependencies explicitly stated
- Build/test commands specific to the project type
</workflow>
<research_task>
For the entire project described in the master plan, research and gather:
1. **Project-Wide Analysis:**
- Project type, technology stack, versions
- Project structure and folder organization
- Coding conventions and naming patterns
- Build/test/run commands
- Dependency management approach
2. **Code Patterns Library:**
- Collect all existing code patterns
- Document error handling patterns
- Record logging/debugging approaches
- Identify utility/helper patterns
- Note configuration approaches
3. **Architecture Documentation:**
- How components interact
- Data flow patterns
- API conventions
- State management (if applicable)
- Testing strategies
4. **Official Documentation:**
- Fetch official docs for all major libraries/frameworks
- Document APIs, syntax, parameters
- Note version-specific details
- Record known limitations and gotchas
- Identify permission/capability requirements
Return a comprehensive research package covering the entire project context.
</research_task>
<plan_template>
# {FEATURE_NAME}
## Goal
{One sentence describing exactly what this implementation accomplishes}
## Prerequisites
Make sure that the use is currently on the `{feature-name}` branch before beginning implementation.
If not, move them to the correct branch. If the branch does not exist, create it from main.
### Step-by-Step Instructions
#### Step 1: {Action}
- [ ] {Specific instruction 1}
- [ ] Copy and paste code below into `{file}`:
```{language}
{COMPLETE, TESTED CODE - NO PLACEHOLDERS - NO "TODO" COMMENTS}
```
- [ ] {Specific instruction 2}
- [ ] Copy and paste code below into `{file}`:
```{language}
{COMPLETE, TESTED CODE - NO PLACEHOLDERS - NO "TODO" COMMENTS}
```
##### Step 1 Verification Checklist
- [ ] No build errors
- [ ] Specific instructions for UI verification (if applicable)
#### Step 1 STOP & COMMIT
**STOP & COMMIT:** Agent must stop here and wait for the user to test, stage, and commit the change.
#### Step 2: {Action}
- [ ] {Specific Instruction 1}
- [ ] Copy and paste code below into `{file}`:
```{language}
{COMPLETE, TESTED CODE - NO PLACEHOLDERS - NO "TODO" COMMENTS}
```
##### Step 2 Verification Checklist
- [ ] No build errors
- [ ] Specific instructions for UI verification (if applicable)
#### Step 2 STOP & COMMIT
**STOP & COMMIT:** Agent must stop here and wait for the user to test, stage, and commit the change.
</plan_template>
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.