From rpi
iterate on structure outline based on user feedback. Don't use if you already used create-structure-outline
How this skill is triggered — by the user, by Claude, or both
Slash command
/rpi:iterate-structure-outlineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are iterating on an existing structure outline document based on user feedback.
You are iterating on an existing structure outline document based on user feedback.
docPath: Path to the existing structure outline document (e.g., .humanlayer/tasks/ENG-XXXX-description/NN-structure-outline-DESCRIPTION.md)If the user calls this with no instructions or feedback, ask them for their feedback:
I'm ready to iterate on the structure outline. What feedback or changes would you like me to incorporate? For example:
- Phase reorganization
- Scope changes (add/remove items)
- Answers to open questions
- Additional context or requirements
Then wait for the user's feedback before proceeding.
Read all input documents FULLY:
Check for related task content:
.humanlayer/tasks/TASKNAME is mentioned, use ls .humanlayer/tasks/TASKNAMEIf the user gives any input:
Spawn sub-agents for follow-up research (if needed):
For deeper investigation:
Do not run agents in the background - FOREGROUND AGENTS ONLY.
Process the feedback:
Update document (if changes needed):
docPathUpdate the user
Read({SKILLBASE}/references/structure_outline_final_answer.md)When documents conflict, the most recent document wins: structure outline > design discussion > research > ticket
## Cloud PermalinksWhen you write or edit documents in .humanlayer/tasks/, a cloud permalink is automatically provided in the hook response.
additionalContext after Write/Edit/MultiEdit/Read operationshttp(s)://{DOMAIN}/artifacts/{artifactId}When writing markdown files that contain code blocks showing other markdown (like README examples or SKILL.md templates), use 4 backticks (````) for the outer fence so inner 3-backtick code blocks don't prematurely close it:
# Example README
## Installation
```bash
npm install example
```
The goal of this document is to be concise and human readable. Be tasteful and thoughtful about how and where you include code snippets, and prefer highlighting signature changes rather than entire code blocks, unless the user explicitly asks for them. The structure outline is our "c header files", the plan will include the function definitions.
Not every phase requires manual validation, don't put steps for manual validation just to have them.
There's a good chance that if a phase cannot be manually checked, its either too small or not vertical enough. The goal of manual validation is to avoid getting to the end of a 1000+ line code change and then having to figure out which part went wrong.
Automated testing is always better than manual testing - be thoughtful based on your knowledge of the codebase and testing patterns, and be clear about which tests are manual versus automated.
npx claudepluginhub jturner421/rpi-skillsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.