Skip to content

docs(#236): add bidirectional cross-referencing guidance for problem docs #274

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
fullsend-ai-coder wants to merge 1 commit into from
Closed

docs(#236): add bidirectional cross-referencing guidance for problem docs #274

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ Fullsend is a platform for fully autonomous agentic development for GitHub-hoste
- Problem documents (`docs/problems/`) should present multiple options with trade-offs, not prescribe single solutions.
- Each problem document has an "Open questions" section — this is where unresolved issues live.
- When adding new problem areas, create a new file in `docs/problems/` and link it from `README.md`.
- When a new problem doc covers a topic already mentioned in existing docs, search for references to the concept across `docs/problems/` and add backlinks from those existing docs to the new doc in the same PR. This ensures readers can discover the new doc from its related contexts.
- The security threat model (threat priority: external injection > insider > drift > supply chain) should inform all other documents.
- Keep core problem documents organization-agnostic. Organization-specific details belong in `docs/problems/applied/<org-name>/`.
- The target audience for problem documents is any contributor community considering autonomous agents — keep language accessible and avoid presuming solutions.
Expand Down
Loading