메뉴
Transform vague or high-level human intent into a governed Discovery action plan. Activate when intent is unclear, broad, or when multiple discovery steps are required before any artefact is created.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | discovery-high-level-plan |
| description | Transform vague or high-level human intent into a governed Discovery action plan. Activate when intent is unclear, broad, or when multiple discovery steps are required before any artefact is created. |
| license | MIT |
| compatibility | Works with any filesystem-based AI coding agent |
| metadata | {"author":"gaai-framework","version":"1.0","category":"discovery","track":"discovery","id":"SKILL-DISCOVERY-HIGH-LEVEL-PLAN-001","updated_at":"2026-02-26T00:00:00.000Z","status":"stable"} |
| inputs | ["human_intent","contexts/artefacts/** (optional)","contexts/memory/** (selective)"] |
| outputs | ["discovery_action_plan"] |
Activate this skill when:
Typical triggers: "I have an idea for a feature", "Users are dropping during onboarding", "We should rethink pricing", "There's a bug where X happens but we don't know why"
This skill plans — it does not produce artefacts.
Discovery Action Plan
Goal:
<what clarity must be achieved>
Steps:
1. <skill name> — purpose
2. <skill name> — purpose
3. <skill name> — purpose
Validation Gates:
- artefact completeness
- acceptance criteria present
- uncertainties flagged
Ready For Delivery:
yes / no
Blocking Reasons (if any):
- ...
This skill must NOT:
If the next step isn't obvious — plan first. Planning prevents waste more than speed increases output.
Auto-commit changes after a Spec Kit command completes
Research industry standards and best practices, identify viable approaches for a given technical or architectural problem, and produce a structured factual comparison against project-specific constraints. Reports options — does not decide.
Convert raw project structure into clear architectural understanding — module boundaries, data flows, service relationships, and architectural patterns. Activate after codebase-scan during Bootstrap.
Scan all agent and sub-agent definition files in .gaai/core/agents/, extract YAML frontmatter, merge with specialists.registry.yaml, and generate a derived agents-index.yaml at .gaai/core/agents/agents-index.yaml. Activate after adding, modifying, or removing any agent, sub-agent, or specialist entry.
Scan SKILL.md files in .gaai/core/skills/ and .gaai/project/skills/, extract YAML frontmatter, and regenerate separate skills indices for each layer. Core index ships with the OSS framework; project index is project-specific.
Create a high-level map of the project structure and identify architectural pillars, entry points, and module boundaries. Activate at Bootstrap initialization or before architecture extraction.