epic: APM integration — make agentrc output distributable and governed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python, typescript
- Domain
- developer-experience, documentation, tooling
Research direction
Review the completed child issues #91 and #93 and their linked PRs #92 and #94, then check the README cross-documentation work in PR #95. The listed first wave is already implemented, so identify any remaining integration scope before starting work on this epic.
Written by the indexing model from the issue text.
Description
Why
AI coding agents are only as effective as the context they receive. agentrc solves the creation problem — it analyzes real code and generates tailored instructions. But creation without distribution is a dead end. Teams need to share instructions across repos, govern what agent packages are allowed, and audit them in CI.
APM (Agent Package Manager) solves the distribution problem — transitive dependency resolution, security scanning, multi-platform compilation, and enterprise policy enforcement for agent primitives.
Together: agentrc generates. APM distributes. Neither tool needs the other to be useful, but together they close a loop that neither closes alone.
What
This epic tracks the first wave of agentrc × APM integration:
- Readiness scoring — agentrc scores repos on APM adoption (#91)
- Init bridge —
agentrc initdetects APM and offers to set it up (#93) - Cross-documentation — README sections establishing the ecosystem narrative
Key design principles
- agentrc never writes
apm.yml— it delegates toapm init(APM owns its manifest) - Formats are compatible by default —
.instructions.mdfiles work in both tools without conversion - Explicit opt-in — APM is suggested, never imposed;
--yesskips it entirely - Subprocess integration — tools call each other via CLI, respecting the Python/TypeScript boundary
Child issues
- #91 — feat(readiness): Add APM awareness to ai-tooling pillar → PR #92
- #93 — feat(init): Bridge to APM during init → PR #94
- Cross-documentation (README updates) → PR #95
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 94
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 34
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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 microsoft/agentrc
-
agentic-workflows automation readiness
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
microsoft/agentrc#379 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/agentrc#372 · 2 reactions ·
Maintainers usually reply within 1 day
-
[aw] Detection RunsOpenagentic-workflows
Difficulty 5/5 Over a week Newbie friendliness 1/100
microsoft/agentrc#349 · 8 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
All issues in microsoft/agentrc
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
OHDSI/Data2Evidence#3496 ·
Maintainers usually reply within 2 days
-
TaskSecret.vue: replace explicit `any` with real typesPossibly taken @prayas-bit claimed this today. Openarea/frontend good first issue kind/cooldown
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
kestra-io/kestra#20352 · 1 comment ·
Maintainers usually reply within 1 day
-
Bouncer: long messages are re-split at 350 bytes, breaks echo-message reconciliationPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day