Skip to content

docs: add AUTONOMOUS.md - #2479

Merged
kevinmessiaen merged 1 commit into
mainfrom
docs/autonomous-md
May 20, 2026
Merged

docs: add AUTONOMOUS.md#2479
kevinmessiaen merged 1 commit into
mainfrom
docs/autonomous-md

Conversation

@kevinmessiaen

Copy link
Copy Markdown
Member

No description provided.

@kevinmessiaen
kevinmessiaen requested a review from a team as a code owner May 20, 2026 13:43
@kevinmessiaen
kevinmessiaen merged commit d14b451 into main May 20, 2026
21 of 24 checks passed
@kevinmessiaen
kevinmessiaen deleted the docs/autonomous-md branch May 20, 2026 13:44

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refines the documentation for coding agents by introducing a new AUTONOMOUS.md file for agents operating without human oversight and updating AGENTS.md to provide more generalized guidance for interactive assistants. Key changes include standardizing the directory structure for planning documents and updating references from CLAUDE.md to AGENTS.md. Review feedback focused on improving the clarity and consistency of instructions regarding where to save specifications and plans, suggesting more concise wording for these sections.

Comment thread AGENTS.md
– Enter plan mode for ANY non-trivial task (3+ steps or touches multiple libs)
– Brainstorm first (design → spec), then write an implementation plan
– Save specs to `docs/superpowers/specs/`, plans to `docs/superpowers/plans/`
– Save specs and plans in the repo's established planning docs. Prefer `docs/specs/` and `docs/plans/`; if the repo already uses another planning directory, follow that convention.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The wording here is a bit redundant. It's better to provide a clear, concise instruction for the agent to follow. Consider simplifying the sentence to make it more direct.

Suggested change
– Save specs and plans in the repo's established planning docs. Prefer `docs/specs/` and `docs/plans/`; if the repo already uses another planning directory, follow that convention.
– Save specs and plans to `docs/specs/` and `docs/plans/` (or the repo's established planning directory).
Comment thread AGENTS.md

## Task Management
1. Brainstorm → Spec → Plan — save to `docs/superpowers/specs/` and `docs/superpowers/plans/`
1. Brainstorm → Spec → Plan — save to the repo's established planning docs, preferably `docs/specs/` and `docs/plans/`

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This line repeats the same instruction as line 10. For better maintainability and to avoid confusion, it's best to keep these instructions consistent and concise.

Suggested change
1. Brainstorm → Spec → Plan — save to the repo's established planning docs, preferably `docs/specs/` and `docs/plans/`
1. Brainstorm → Spec → Plan — save to `docs/specs/` and `docs/plans/` (or the repo's established planning directory)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant