Skip to content

docs: add new SDD introductions and tools#4

Open
mvance wants to merge 2 commits intozhimin-z:mainfrom
mvance:add-sdd-resources
Open

docs: add new SDD introductions and tools#4
mvance wants to merge 2 commits intozhimin-z:mainfrom
mvance:add-sdd-resources

Conversation

@mvance
Copy link

@mvance mvance commented Feb 21, 2026

This PR adds several new resources to the Awesome Spec-Driven Development list:

  • Added 'Introductions' section with O'Reilly article on AI agent specs.
  • Added 'adversarial-spec', 'BMAD-METHOD', and 'get-shit-done' to the Tools section.

Resources were added in alphabetical order where applicable.

@gemini-code-assist
Copy link

Summary of Changes

Hello @mvance, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request expands the 'Awesome Spec-Driven Development' list by incorporating new resources. It introduces a dedicated section for introductory materials, specifically an article focusing on AI agent specifications, and enriches the existing tools section with three additional entries. These updates aim to provide a more comprehensive and current collection of resources for the community.

Highlights

  • New Introductions Section: A new 'Introductions' section was added to the README, featuring an O'Reilly article on writing specifications for AI agents.
  • Expanded Tools Section: Three new tools, 'adversarial-spec', 'BMAD-METHOD', and 'get-shit-done', were added to the 'Tools' section, enhancing the list of resources for spec-driven development.
Changelog
  • README.md
    • Added a new 'Introductions' section.
    • Included a link to an O'Reilly article titled 'How to write a good spec for AI agents' within the new 'Introductions' section.
    • Inserted 'adversarial-spec' into the 'Tools' section, maintaining alphabetical order.
    • Inserted 'BMAD-METHOD' into the 'Tools' section, maintaining alphabetical order.
    • Inserted 'get-shit-done' into the 'Tools' section, maintaining alphabetical order.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

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

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 adds a new 'Introductions' section and three new tools to the Awesome Spec-Driven Development list. The changes are well-structured, and the new entries are added in alphabetical order as intended. I have one suggestion to improve the description of one of the new tools to make it more informative for readers.

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