Replies: 1 comment
-
|
Thanks for the careful write-up, and good call not guessing the fix. It's a doc bug, not a design choice. The action is the correct one: plans go to So the fix is to correct the READMEs ( Side note since you mentioned intent: This also ties into #276, where implement can fabricate a substitute when it can't resolve the plan path. I'll fold the doc fix in there. Does that match what you were seeing, or did you hit it somewhere else in the flow? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Body:
Summary
Heads-up: the
aidd-dev:01-planskill documents two different outputdirectories depending on which file you read. Flagging it so a maintainer can
decide which is the intended convention —
plans/ortasks/.The inconsistency
Plugin:
aidd-devv1.2.1README —
plugins/aidd-dev/skills/01-plan/README.md(line 42):Action —
plugins/aidd-dev/skills/01-plan/actions/01-plan.md:plan_path: aidd_docs/tasks/<yyyy_mm>/...aidd_docs/tasks/<yyyy_mm>/So the skill writes to
aidd_docs/tasks/(the action is what runs), while theREADME documents
aidd_docs/plans/.Note
The two names carry different intent —
tasks/groups the plan with downstreamartifacts (README.md line 72 already describes
tasks/as "Specs, plans, runsummaries"), whereas
plans/would give generated plans their own namespace.So this may be a real design choice rather than a simple typo, which is why I'm
reporting it rather than guessing the fix.
Beta Was this translation helpful? Give feedback.
All reactions