Use Graphify queries for plan-stage discovery
Maintainers usually reply within 1 day
@hhpatel14 is already working on this.
Since Aug 18, 2026.
Assessment
This issue has not been assessed yet.
Description
Summary
Update the plan-stage skill to use Graphify CLI queries for project discovery after graphify update.
Rationale
The plan stage must use graph-aware discovery instead of manually reading graphify-out/graph.json. Graphify queries provide focused architecture, dependency, impact, and pattern information. This reduces unnecessary source-file reads.
Affected area
harness/skills/plan/SKILL.md
Required changes
- Add a Graphify query reference for:
graphify query "<question>"graphify path "A" "B"graphify explain "X"graphify affected "X"
- Define a discovery workflow that queries architectural layers, central nodes, migration patterns, dependency paths, and impact before phase ordering.
- Define community-to-phase mapping guidance. Use domain-skill phase names and ordering when a domain skill is present.
- Add a selective-reading strategy and budget.
- Require a Graphify query before each source-file read.
- Prohibit manual reads of
graphify-out/graph.jsonduring planning.
Acceptance criteria
- The plan skill directs agents to use Graphify CLI queries for graph discovery.
- The plan skill includes query-first rules for source-file reading.
- The plan skill defines phase mapping and selective-reading guidance.
- The plan skill does not instruct agents to manually inspect
graphify-out/graph.json.
Backlinks
- Pull request: https://github.com/konveyor/agentic-controller/pull/98
- Review discussion: https://github.com/konveyor/agentic-controller/pull/98#discussion_r3807698088
- Requested by: @savitharaghunathan
- Dominant language
- Go
- Stars
- 5
- Forks
- 13
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 27
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from konveyor/agentic-controller
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
konveyor/agentic-controller#305 ·
Maintainers usually reply within 1 day
-
bug stream/controller
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
konveyor/agentic-controller#164 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
konveyor/agentic-controller#124 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
konveyor/agentic-controller#323 ·
Maintainers usually reply within 1 day
-
Provider-aware Gateway verification for aws-bedrock / gcp-vertex-ai, so bad credentials fail at verify rather than mid-runPossibly taken @ibolton336 claimed this 2 days ago. Openenhancement stream/controller
konveyor/agentic-controller#304 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in konveyor/agentic-controller
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TUM-Dev/Campus-Backend#678 ·
Maintainers usually reply within 1 day
-
fix(app): fail closed if GetGeneralSetting fails during initializationPossibly taken @kalavt claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tsukumogami/tsuku#2813 ·
Maintainers usually reply within 1 day
-
component:obi contribfest go test
Difficulty 2/5 Under an hour Newbie friendliness 83/100
open-telemetry/opentelemetry-ebpf-instrumentation#4143 · 1 comment ·
Maintainers usually reply within 1 day