e03b00843a
Adds decisions and process-lessons from recent reflections. Updates decompose and orchestrate SKILL.md with operational improvements. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
18 lines
1.0 KiB
Markdown
18 lines
1.0 KiB
Markdown
# Process Lessons
|
|
|
|
## Container agent prompts need high detail for quality output
|
|
|
|
Container agents produce substantial output (e.g., 426-line spec) when given detailed, structured prompts. Invest time in prompt crafting during `/decompose` — the agent has no conversation history to draw from.
|
|
|
|
## Use 3+ parallel research agents before planning
|
|
|
|
Survey different domains (competing tools, best practices, user patterns) in parallel before committing to an architecture. The breadth of input prevents tunnel vision during planning.
|
|
|
|
## The decompose/orchestrate/loop pattern creates a manager session
|
|
|
|
Human drives strategy via `/decompose`, agents execute via `/orchestrate`, and `/loop 2m /orchestrate` auto-polls progress. The human's role shifts from doing to reviewing and steering.
|
|
|
|
## Always run validate-skill before committing skill changes
|
|
|
|
The validator catches restriction violations (uncovered binaries, `$()` substitution, `${VAR}` syntax) that silently break skills at load time. Run it as a pre-commit gate, not an afterthought.
|