Skip to content

Add Agentic Engineering - #4286

Open
jordimas wants to merge 2 commits into
sindresorhus:mainfrom
jordimas:add-agentic-engineering
Open

jordimas wants to merge 2 commits into
sindresorhus:mainfrom
jordimas:add-agentic-engineering

Conversation

@jordimas

@jordimas jordimas commented Jun 25, 2026 •

Copy link
Copy Markdown

https://github.com/jordimas/awesome-agentic-engineering

Agentic Engineering is the emerging discipline where AI agents autonomously plan, write, test, and evolve software under human goals. This list curates first-party docs, canonical essays, mature tools, and key papers engineering teams need to adopt agentic workflows.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

  • Fully AI-generated pull requests are not accepted.
  • Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
  • Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
  • You have to review at least 4 other open pull requests. My contributions:
  • Add Singapore CS1010 #4275 (comment)
  • Add Company as a Service #4205 (comment)
  • Add Arabic Tools #4271 (comment)
  • Add Testing Tools #4265 (comment)
  • You have read and understood the instructions for creating a list.
  • This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
    • ✅ Add Swift
    • ✅ Add Software Architecture
    • ❌ Update readme.md
    • ❌ Add Awesome Swift
    • ❌ Add swift
    • ❌ add Swift
    • ❌ Adding Swift
    • ❌ Added Swift
  • Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
    • ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
    • ✅ - [Framer](…) - Prototyping interactive UI designs.
    • ❌ - [iOS](…) - Resources and tools for iOS development.
    • ❌ - [Framer](…)
    • ❌ - [Framer](…) - prototyping interactive UI designs
  • Your entry should be added at the bottom of the appropriate category.
  • The title of your entry should be title-cased and the URL to your list should end in #readme.
    • Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.
  • No blockchain-related lists.
  • The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

  • Has been around for at least 30 days.
    That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
  • Is not AI-generated.
  • Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
  • The default branch should be named main, not master.
  • Includes a succinct description of the project/theme at the top of the readme. (Example)
    • ✅ Mobile operating system for Apple phones and tablets.
    • ✅ Prototyping interactive UI designs.
    • ❌ Resources and tools for iOS development.
    • ❌ Awesome Framer packages and tools.
  • It's the result of hard work and the best I could possibly produce.
    If you have not put in considerable effort into your list, your pull request will be immediately closed.
  • The repo name of your list should be in lowercase slug format: awesome-name-of-list.
    • ✅ awesome-swift
    • ✅ awesome-web-typography
    • ❌ awesome-Swift
    • ❌ AwesomeWebTypography
  • The heading title of your list should be in title case format: # Awesome Name of List.
    • ✅ # Awesome Swift
    • ✅ # Awesome Web Typography
    • ❌ # awesome-swift
    • ❌ # AwesomeSwift
  • Non-generated Markdown file in a GitHub repo.
  • The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
  • Not a duplicate. Please search for existing submissions.
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
  • Includes a project logo/illustration whenever possible.
    • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
    • The image should link to the project website or any relevant website.
    • The image should be high-DPI. Set it to a maximum of half the width of the original image.
    • Don't include both a title saying Awesome X and a logo with Awesome X. You can put the header image in a # (Markdown header) or <h1>.
  • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
  • Includes the Awesome badge.
    • Should be placed on the right side of the readme heading.
      • Can be placed centered if the list has a centered graphics header.
    • Should link back to this list.
  • Has a Table of Contents section.
    • Should be named Contents, not Table of Contents.
    • Should be the first section in the list.
    • Should only have one level of nested lists, preferably none.
    • Must not feature Contributing or Footnotes sections.
  • Has an appropriate license.
    • We strongly recommend the CC0 license, but any Creative Commons license will work.
      • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
    • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
    • Place a file named license or LICENSE in the repo root with the license text.
    • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
    • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
  • Has contribution guidelines.
    • The file should be named contributing.md. The casing is up to you.
    • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
    • The section should not appear in the Table of Contents.
  • All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
  • Has consistent formatting and proper spelling/grammar.
    • The link and description are separated by a dash.
      Example: - [AVA](…) - JavaScript test runner.
    • The description starts with an uppercase character and ends with a period.
    • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
  • Does not use hard-wrapping.
  • Does not include a CI (e.g. GitHub Actions) badge.
    You can still use a CI for linting, but the badge has no value in the readme.
  • Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

@jordimas jordimas changed the title Add agentic engineering Add Agentic Engineering Jun 25, 2026
@sindresorhus

Copy link
Copy Markdown
Owner

Thanks for making an Awesome list! 🙌

It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

@zlc000190

Copy link
Copy Markdown

Thanks for putting this together. One concrete thing to fix before merge: the PR body still contains the template placeholder lines ( / ). I would remove those placeholders entirely so the submission reads as a clean, fully-completed awesome PR rather than a partially edited template.

@jordimas

Copy link
Copy Markdown
Author

Thanks for putting this together. One concrete thing to fix before merge: the PR body still contains the template placeholder lines ( / ). I would remove those placeholders entirely so the submission reads as a clean, fully-completed awesome PR rather than a partially edited template.

Thanks. I fixed all of these. If I missed anything please let me know.

@jordimas

Copy link
Copy Markdown
Author

Thanks for making an Awesome list! 🙌

It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

Thanks. I checked again and made several small mistakes. If anything is still missing I will appreciate if you can be more specific. Thanks so much!

@jordimas

Copy link
Copy Markdown
Author

unicorn

@dvershinin

Copy link
Copy Markdown

A few things worth addressing:

1. Entry description reads like a list description, not a topic description
The proposed entry: "Practices and tooling for AI agent-driven software development."

The word "tooling" puts this in the same pattern as the bad example: - [iOS](…) - Resources and tools for iOS development. The description should explain what the subject matter IS, not what the list contains. Something like "Software development discipline where AI agents autonomously plan, write, test, and evolve code under human-defined goals." describes the concept rather than the list's contents.

2. Key Papers section has only one entry
A section with a single item doesn't read like a curated selection — it's a singleton. Either expand it with additional key papers worth reading, or fold that one entry into an adjacent section (e.g. Case Studies and Practical Advice or Standards).

3. GitHub Stars badges
Many entries carry inline ![Stars](https://img.shields.io/github/stars/...) badges. The guidelines prohibit CI badges and, while stars badges are different in nature, they add noise and are non-standard across accepted awesome lists. It's worth running awesome-lint with these present to confirm they don't trigger a warning — and removing them is the safer path regardless.

@dvershinin dvershinin mentioned this pull request Jul 5, 2026
32 of 33 tasks
@rodchalski

Copy link
Copy Markdown

Review of awesome-agentic-engineering

Good list overall — well-organized and clearly curated. A few things worth addressing:

  1. Inline star-count shields — entries include ![Stars](https://img.shields.io/github/stars/...) inline after each link. These are dynamic badges that change over time and add noise to a static curated list. The CI badge rule (no CI badges) exists partly for this reason. Even though these aren't CI badges, the principle is the same: badges add external dependencies and visual clutter. I'd recommend removing them.

  2. Horizontal rule dividers — --- separators appear between sections (after the Contents list and between most sections). Standard awesome lists don't use these; section headings are sufficient to divide content. This creates visual inconsistency compared to the rest of the awesome project.

  3. Sparse sections — the "Standards" section has a single entry (OWASP Top 10 for Agentic Applications). A section with one item is usually a sign it should either be merged into another section or expanded. Same with "Spec-Driven Development" which has only 2 entries.

  4. PDF direct links — one entry links directly to a PDF: https://cdn.openai.com/business-guides-and-resources/a-practical-guide-to-building-agents.pdf. This is fragile (CDN URLs change) and the document has a canonical page at openai.com that would be more stable to link to.

@rodchalski rodchalski mentioned this pull request Jul 15, 2026
31 of 34 tasks
@Egv2

Egv2 commented Jul 15, 2026

Copy link
Copy Markdown

nice list, well organized and the categories make sense. one significant issue though:

  1. every entry has a star badge next to it. the awesome-list guidelines explicitly say "don't add a badge to your entry, it's noise." you'll need to remove all the star badges from the entries before this can be merged.

  2. the "Commercial Offering" subsection under "Code-Focused Agent Tools" mixes open source and commercial tools in a way that might confuse readers. consider whether that split is necessary or if you can just list them all together.

the star badge thing is the main blocker here :)

@martinholovsky

Copy link
Copy Markdown

Reviewed as part of my PR (#4336). Nice, tightly-scoped list — a few substantive suggestions:

  • Per-item star badges are inconsistent. 26 entries carry a img.shields.io/github/stars badge, but the non-repo entries (Cursor, the Anthropic/OpenAI docs, the PDF guide) don't — so the column looks ragged. The Awesome project generally discourages decorative badges in entries; I'd drop all of them for consistency.
  • "Commercial Offering" is mislabeled. Gemini CLI and Codex under that subheading are both Apache-2.0 open source (I checked the repos), sitting opposite an "Open Source — Model-Agnostic" group. The open-source/commercial split is inaccurate — consider "first-party/vendor" vs "third-party," or model-agnostic vs model-specific.
  • Miscategorized entry. everything-claude-code is a prompts/resources repo but lives under "Case Studies and Practical Advice," which is otherwise real-team write-ups and talks. It reads as a tool, not a case study.
  • Minor: the GLM-5 paper links to the arXiv PDF (/pdf/2602.15763); convention is the abstract page (/abs/…).

Top description is properly theme-first, and structure is clean otherwise.

@martinholovsky martinholovsky mentioned this pull request Jul 17, 2026
35 tasks done

@DasterProkio DasterProkio left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I reviewed the catalog entry and the current linked list, ran awesome-lint (it passes), and checked all 27 GitHub repositories referenced by the README.

One list-level blocker remains: RooCodeInc/Roo-Code is currently archived, while the submission requirements explicitly exclude archived projects from the main list. Please remove it or move it to a separate archived-reference file.

The taxonomy could also be made more objective: Commercial Offering currently groups open-source Gemini CLI, Claude Code, and Codex repositories together with the closed-source Cursor product. A label such as Vendor-Specific Tools, or a split based on source availability, would tell readers what distinction the section actually represents.

@DasterProkio DasterProkio mentioned this pull request Aug 8, 2026
31 tasks done

This branch has not been deployed

No deployments
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.

8 participants