Skip to content

docs: keep design docs in a neutral folder layout - #14

Merged
oonid merged 2 commits into
mainfrom
docs/neutral-docs-layout
Oct 17, 2026
Merged

oonid merged 2 commits into
mainfrom
docs/neutral-docs-layout

Conversation

@oonid

@oonid oonid commented Oct 17, 2026 •

Copy link
Copy Markdown
Owner

Keeps the docs layout neutral while AGENTS.md still points agents at the Superpowers workflow.

  • docs/superpowers/specs/2026-09-13-proot-engine-library-design.md moves to docs/design/proot-engine-library.md (content unchanged); the README link follows.

  • The AGENTS.md "Superpowers Workflow" section is unchanged and gains one rule: the skills' documents go in the neutral layout instead of their default docs/superpowers/ folders, with design specs in docs/design/<topic>.md and implementation plans in docs/plans/<topic>.md.

  • Separate commit: README described docs/proot-improvement.md as 29 sections; it has 35.

After this, no docs/superpowers/ folder remains. Docs only. Replaces the cancelled #13; the background-sessions design follows in its own PR, at docs/design/background-sessions.md.

Design specs lived under docs/superpowers/specs/, the default folder of
the Superpowers skills. The proot-engine library spec moves to
docs/design/proot-engine-library.md (README link updated), and the
Superpowers Workflow section in AGENTS.md now says where the skills'
documents go: specs in docs/design/<topic>.md, plans in
docs/plans/<topic>.md.
@oonid
oonid force-pushed the docs/neutral-docs-layout branch from 2615de4 to f5eb2e4 Compare October 17, 2026 15:36
@oonid oonid changed the title docs: use a neutral layout for design docs docs: keep design docs in a neutral folder layout Oct 17, 2026
README still described docs/proot-improvement.md as 29 sections; it has
35 since sections 30-35 were added (auxv, SO_PEERCRED, chroot, build
warnings, fake_id0 cleanups, app cache group).
@oonid
oonid merged commit 51e978c into main Oct 17, 2026
1 check passed
@oonid
oonid deleted the docs/neutral-docs-layout branch October 17, 2026 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant