Blog-Writing Topics Product Launch Exemplary Slides
EDM On A Good News For A New Launch Of Product Feature Users running both Compound Knowledge and Compound Engineering end up with two separate plan folders: Simon-Kucher Headquarters
- CK writes to
plans/ (root) - CE writes to
docs/plans/
Sentence Starters GCSE Creative Writing Both plugins are explicitly designed as a pair — CE's README links to CK as its knowledge-work equivalent — so this inconsistency stands out. When cross-referencing work across both workflows, you have to check two places. Article In Newspaper Just Writing
Bank Of America Private Banking Product Launch Exemplary Slides
Photos For Product Launch CK already uses docs/ as its primary output namespace — docs/knowledge/ and docs/solutions/ are both established conventions shared by both plugins. plans/ at the root is the odd one out. Moving it to docs/plans/ would make CK's full output footprint: Instagram PFP Of A New Story
docs/knowledge/ ← /kw:compound output (already aligned) docs/solutions/ ← CE output (already aligned) docs/plans/ ← /kw:plan, /kw:brainstorm output (currently misaligned)
Wireless Credit Cards Machines Product Launch Exemplary Slides
Blog-Writing Topics Four skill files, find/replace plans/ → docs/plans/: Blog Post About Products
skills/kw-brainstorm/SKILL.md — search path + save path (3 references) skills/kw-plan/SKILL.md — origin doc search + write path (4 references) skills/kw-work/SKILL.md — plan load fallback path (1 reference) skills/kw-confidence/SKILL.md — save path (1 reference)
Bank Of America Private Banking Plus README.md — the line "Works with any project that has a plans/ directory" would need updating. Sample Of Website Launch Template
Tarot Business Cards Product Launch Exemplary Slides
Wireless Credit Cards Machines For existing users with files in plans/, a one-line note in the changelog (and optionally README) would cover it. The files themselves are plain markdown — a mv plans/* docs/plans/ is all that's needed. Blogger Writing
Tarot Business Cards Happy to open a PR if you're open to it. Flagging as an issue first in case you have context on why plans/ was chosen separately, or want to handle the migration note your way. Launch Plan Template PDF
Blog-Writing Topics Product Launch Exemplary Slides
EDM On A Good News For A New Launch Of Product Feature Users running both Compound Knowledge and Compound Engineering end up with two separate plan folders: Simon-Kucher Headquarters
plans/(root)docs/plans/Sentence Starters GCSE Creative Writing Both plugins are explicitly designed as a pair — CE's README links to CK as its knowledge-work equivalent — so this inconsistency stands out. When cross-referencing work across both workflows, you have to check two places. Article In Newspaper Just Writing
Bank Of America Private Banking Product Launch Exemplary Slides
Photos For Product Launch CK already uses
docs/as its primary output namespace —docs/knowledge/anddocs/solutions/are both established conventions shared by both plugins.plans/at the root is the odd one out. Moving it todocs/plans/would make CK's full output footprint: Instagram PFP Of A New StoryWireless Credit Cards Machines Product Launch Exemplary Slides
Blog-Writing Topics Four skill files, find/replace
plans/→docs/plans/: Blog Post About Productsskills/kw-brainstorm/SKILL.md— search path + save path (3 references)skills/kw-plan/SKILL.md— origin doc search + write path (4 references)skills/kw-work/SKILL.md— plan load fallback path (1 reference)skills/kw-confidence/SKILL.md— save path (1 reference)Bank Of America Private Banking Plus
README.md— the line "Works with any project that has aplans/directory" would need updating. Sample Of Website Launch TemplateTarot Business Cards Product Launch Exemplary Slides
Wireless Credit Cards Machines For existing users with files in
plans/, a one-line note in the changelog (and optionally README) would cover it. The files themselves are plain markdown — amv plans/* docs/plans/is all that's needed. Blogger WritingTarot Business Cards Happy to open a PR if you're open to it. Flagging as an issue first in case you have context on why
plans/was chosen separately, or want to handle the migration note your way. Launch Plan Template PDF