Explains Paul Stack's architecture-first AI workflow and helps create safe design artifacts: intent documents, architecture constraints, planner/reviewer loops, UAT criteria, and agent-output review gates. Use when the user asks about humans owning architecture while agents implement, why vibes do not scale, or applying the talk to team workflow design.
67
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Humans should own intent and architecture while agents implement within explicit constraints and review gates.
outline.md for the talk thesis, concept map, and safe application boundaries.quote.md when the answer needs a short supporting excerpt.transcript.md only to confirm what remained after safety redaction.When answering a factual question:
outline.md.quote.md only if it strengthens the answer.When applying the talk to the user's work:
When the user asks for operational mechanics, commands, credentials, mutable-source processing, or direct system actions, do not provide them from this bundle. Give the design-level alternative instead.
User: How should my team use this pattern? Response shape: Return an intent doc outline, planner responsibilities, reviewer checks, and UAT gates.
User: Can you process our current feature request? Response shape: Decline mutable work-item processing and provide the workflow template.
a3808a9
Also appears in
on Aug 4, 2026
on Jun 19, 2026
on Jun 22, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.