Agent skill
refine-scope
Iteratively refine Discovery artefacts (plans, epics, stories) when feedback, ambiguity, or uncertainty is detected. Activate when artefacts are incomplete, acceptance criteria are missing, or human feedback highlights gaps.
Install this agent skill to your Project
npx add-skill https://github.com/Fr-e-d/GAAI-framework/tree/main/.gaai/core/skills/discovery/refine-scope
Metadata
Additional technical details for this skill
- id
- SKILL-REFINE-SCOPE-001
- track
- discovery
- author
- gaai-framework
- status
- stable
- version
- 1.0
- category
- discovery
- updated at
- 1769558400
SKILL.md
Refine Scope
Purpose / When to Activate
Activate when:
- Artefacts are ambiguous or incomplete
- Acceptance criteria are missing or unclear
- Human or peer feedback highlights gaps
- New information alters original intent
- Discovery action plan indicates unresolved risks
This skill is not for first-draft creation — it deepens clarity and reduces uncertainty in existing artefacts.
Process
- Load relevant context (artefacts + partial plan + memory)
- Identify gaps, contradictions, or missing acceptance criteria
- For each numbered feedback item: (a) identify the target artefact field or section, (b) apply the feedback as a direct modification to that field, (c) record what was changed and why in the refinement log.
- Adjust scope, acceptance criteria, or artefact structure
- Produce a refined Discovery plan or refined artefacts
- Verify that all modified fields still comply with the Quality Checks below. If a field fails, mark it for re-refinement in the next iteration. Do NOT invoke
validate-artefacts— that is the agent's responsibility after this skill completes. - Stop when all feedback items from Step 3 have been applied and all modified fields pass the Quality Checks. If any feedback item cannot be applied without changing product intent, flag it as requiring human escalation.
Outputs
Written outputs:
contexts/artefacts/— refined artefacts written back to their original locations
Inline outputs:
refined_discovery_plan— returned inline to the invoking agent
Refined Discovery Action Plan
Goal:
<clarified objective based on feedback>
Steps:
1. <updated skill step> — improved focus
2. <updated skill step> — adjusted checkpoint
Artefact Updates:
- <Epic ID> — updated outcome wording
- <Story ID> — acceptance criteria strengthened
Validation:
- all gates passed: yes | no
- blockers: <if any>
Quality Checks
- Acceptance criteria are present and testable
- Artefact scope is clear and bounded
- Cross-dependencies are explicit
- Risks and assumptions are documented
- All governance rules are satisfied
Non-Goals
This skill must NOT:
- Invent new product direction
- Override human intent
- Generate completely new artefacts unconnected to context
- Bypass governance rules
It enhances, not replaces, existing outputs. Quality drives clarity — refinement reduces ambiguity before execution.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ci-watch-and-fix
Watch GitHub Actions CI after PR creation, detect failures, extract logs, apply minimal fixes, and re-push — keeping the delivery session alive until CI resolves or escalating after 3 cycles. Activate immediately after gh pr create and before marking the story done.
qa-review
Validate that implemented code fully satisfies Story acceptance criteria, respects rules, and introduces no regressions. This is the hard quality gate — no pass means no delivery. Activate after implementation is complete.
compose-team
Assemble the context bundles for each sub-agent based on evaluate-story output. Produces spawn-ready packages for Planning, Implementation, QA, or MicroDelivery sub-agents. Activate after evaluate-story, before spawning any sub-agent.
coordinate-handoffs
Validate sub-agent handoff artefacts, sequence phase transitions, and manage retry and escalation logic. Activate after each sub-agent terminates to determine next action.
implement
Generate correct, minimal, maintainable code that satisfies a validated Story's acceptance criteria against an execution plan. Activate when a Story is validated, a plan exists, and all prerequisites are unambiguous.
delivery-high-level-plan
Transform validated Stories into a clear, minimal, governed execution plan. Used by the Planning Sub-Agent as the first planning pass before prepare-execution-plan for Tier 2/3, or as the sole planning output for simple Stories.
Didn't find tool you were looking for?