prd(ai tools): Add draft PRD for AI repo tooling #15628
Conversation
| - Upstream distros (Fedora) and how specs are sourced | ||
| - The overlay system and when to use it | ||
|
|
||
| 3. **azldev Tool Reference** |
There was a problem hiding this comment.
I'm open to considering it more, but I don't think the azldev reference nor the TOML reference belongs in this repo. It should be linked from here; but it belongs with the azldev project itself.
There will be other project repos that equally need this information too.
There was a problem hiding this comment.
My thinking was have the azldev tool able to emit these files and regenerate/add them to repos. The reality is if want the ai to understand these files we need the instructions files etc. They can either be repo specific, or global for the user, but I'm not a fan of bloating the agents' contexts for ALL projects just to support that. Much better to just have them where they are actually used.
There was a problem hiding this comment.
Discussed offline; what's important to me is that the source of truth for the docs be in the same repo as azldev. There will be multiple repos with TOML files that use azldev and the same schema. I care less about duplication than I do about there being divergent versions of the docs that are independently edited.
Provided there's a way for us to accomplish this, I'm okay with them getting checked in under a dir that's clearly marked as generated/cached content if it helps the AIs.
prd/agent-instructions.prd.md
Outdated
|
|
||
| **Versioning and Compatibility Considerations:** | ||
|
|
||
| When updating packages, agents MUST be cautious about version changes: |
There was a problem hiding this comment.
I think the update policy should be separated out and will end up being differentiated between different segments of the repo.
There was a problem hiding this comment.
My hope was it would be encoded as part of the azldev component, which we can just have the agents query. Doesn't necessarily need to be in any specific spot in the repo.
There was a problem hiding this comment.
I think we're on the same page: policy should be encoded in TOML files. (I didn't want to encode the policy in agent instructions.) Agents should be able to understand that encoded policy, of course.
| @@ -0,0 +1,608 @@ | |||
| # PRD: Agent Instructions and Skills for Azure Linux | |||
|
|
|||
| Title: PRD: Agent Instructions and Skills for Azure Linux | |||
There was a problem hiding this comment.
Thanks for getting the ball rolling with this!
|
Can we place any PRDs for this repo under |
|
Add section on using control tower? |
|
explicitly version the configs (generate them via azldev tool?) |
2 participants
Initial draft PRD for AI tooling support in the distro repo