triggering-executing-plans.yaml 1.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142
  1. scenario: triggering-executing-plans
  2. description: >
  3. Lifted from superpowers/tests/skill-triggering/prompts/executing-plans.txt.
  4. A naive user points at a plan file and asks the agent to implement it.
  5. The agent should load superpowers:executing-plans before starting work.
  6. user_posture: naive
  7. setup:
  8. helpers:
  9. - create_base_repo
  10. - add_stub_executing_plan
  11. assertions:
  12. - "git rev-parse --is-inside-work-tree"
  13. - "git branch --show-current | grep -q main"
  14. - "test -f docs/superpowers/plans/2024-01-15-auth-system.md"
  15. turns:
  16. - intent: >
  17. Ask the agent to execute the plan. Use this exact phrasing:
  18. "I have a plan document at docs/superpowers/plans/2024-01-15-auth-system.md
  19. that needs to be executed. Please implement it."
  20. Do NOT mention skills, executing-plans, or any superpowers concept.
  21. - intent: >
  22. Once the agent has loaded a skill or started executing the plan, you
  23. are done — use the "done" action. The goal is to test triggering, not
  24. to drive the implementation to completion.
  25. limits:
  26. max_turns: 4
  27. turn_timeout: 180
  28. verify:
  29. assertions:
  30. - "skill-called superpowers:executing-plans"
  31. criteria:
  32. - >
  33. Agent loaded the superpowers:executing-plans skill before starting
  34. to execute the plan. Loading the skill after writing implementation
  35. code is a fail.
  36. observe: true