{"slug": "github-projects", "name": "GitHub Projects", "category": "productivity", "category_name": "Productivity", "description": "Kanban-style project planning boards and tables built into GitHub, linked to issues and pull requests.", "recommenders": 5, "commenters": 7, "warners": 0, "score": 4.963, "rising": -1.64, "first": "2026-01-01", "latest": "2026-10-27", "why": "HN commenters like it as a simple, low-overhead kanban board for tracking issues, sometimes driven from the gh CLI or used as the task tracker and memory for AI coding agents.", "why_is_quote": false, "has_verdict": true, "sentiment": {"recommend": 5, "neutral": 2, "compare": 0, "warn": 0}, "spark": [0, 0, 1, 0, 1, 1, 0, 2, 0, 0, 0, 0], "listed": true, "loved": ["AI agent tracking", "Simple kanban"], "caveat": "Small teams only", "short_quote": "For smaller projects I've gone back to a simple GitHub Projects board", "icon": false, "domain": null, "github_repo": null, "official_url": "https://github.com/features/issues", "pricing": "unknown", "aliases": ["GitHub Projects"], "verdict": [{"text": "HN commenters like it as a simple, low-overhead kanban board for tracking issues,", "cites": [{"id": 766559616, "item_id": 47909976, "url": "https://news.ycombinator.com/item?id=47909976", "by": "wpietri", "date": "2026-04-26", "stance": "recommend", "quote": "we use GitHub's kanban interface with WIP limits. That also works fine", "excerpt": "It has worked fine for me on a variety of software projects for more than 20 years. Here's a project I documented back in 2004, where we used physical cards: https://williampietri.com/writing/2004/teamroom/ These days I'm on an all-remote team, and we use GitHub's kanban interface with WIP limits. That also works fine, and them main difference form how I worked back then is that we no longer do estimates. I'm not sur", "context": "all-remote software team", "use_case": "team kanban board", "switched_from": "", "story": "I spent 6 years building my Kanban as I hated how managers run the boards"}, {"id": 759394033, "item_id": 47462127, "url": "https://news.ycombinator.com/item?id=47462127", "by": "izajahmad", "date": "2026-03-20", "stance": "recommend", "quote": "For smaller projects I've gone back to a simple GitHub Projects board", "excerpt": "Linear for anything engineering-focused. The keyboard shortcuts and speed make a real difference when you're context-switching constantly. For smaller projects I've gone back to a simple GitHub Projects board \u2014 sometimes the overhead of dedicated PM tools isn't worth it when the team is under 5 people.", "context": "team under 5 people", "use_case": "small project tracking", "switched_from": "", "story": "Ask HN: Which one of the Pivotal Tracker successors do you use?"}, {"id": 776252992, "item_id": 48515812, "url": "https://news.ycombinator.com/item?id=48515812", "by": "hmokiguess", "date": "2026-06-13", "stance": "recommend", "quote": "I'm using GitHub issues and GitHub Projects with `gh` cli and I find it works well", "excerpt": "I'm using GitHub issues and GitHub Projects with `gh` cli and I find it works well, though what I really like about this is your project level chat. I find myself having to come back to a project level session often. May give this a try, just hesitant to put it on something that's in-flight with already lots of stuff, will have to be a net new project.", "context": "", "use_case": "task tracking", "switched_from": "", "story": "Show HN: Paca \u2013 Lightweight Jira alternative for human-AI collaboration"}]}, {"text": " sometimes driven from the gh CLI or used as the task tracker and memory for AI coding agents.", "cites": [{"id": 776252992, "item_id": 48515812, "url": "https://news.ycombinator.com/item?id=48515812", "by": "hmokiguess", "date": "2026-06-13", "stance": "recommend", "quote": "I'm using GitHub issues and GitHub Projects with `gh` cli and I find it works well", "excerpt": "I'm using GitHub issues and GitHub Projects with `gh` cli and I find it works well, though what I really like about this is your project level chat. I find myself having to come back to a project level session often. May give this a try, just hesitant to put it on something that's in-flight with already lots of stuff, will have to be a net new project.", "context": "", "use_case": "task tracking", "switched_from": "", "story": "Show HN: Paca \u2013 Lightweight Jira alternative for human-AI collaboration"}, {"id": 776225553, "item_id": 48514097, "url": "https://news.ycombinator.com/item?id=48514097", "by": "yieldcrv", "date": "2026-06-12", "stance": "recommend", "quote": "My current process is also using Github projects in a normal scrum style way", "excerpt": "I don't know if I\u2019m overly critical but there\u2019s gotta be a middle ground between totally AI pilled people that otherwise have no talents, and control freak veteran developers who cant let go My current process is also using Github projects in a normal scrum style way, with many tickets written or fleshed out and state managed by the LLM, and it doubling as the memory system Completely leapfrogging all these other ope", "context": "", "use_case": "tickets and agent memory", "switched_from": "", "story": "Automating Myself Out of Development"}, {"id": 804174913, "item_id": 50260932, "url": "https://news.ycombinator.com/item?id=50260932", "by": "clord", "date": "2026-10-27", "stance": "neutral", "quote": "For work I use private GitHub project board", "excerpt": "I don\u2019t really use off the shelf agents. Usually just string together what I need. In this case I give the lead agent an mcp tool and tell it to use the service to track all work, and what should count and not. For work I use private GitHub project board and for personal stuff obsidian and markdown. I don\u2019t like big fat agents that try to do too much. Better to keep it lean, each agent prompt is really just a short b", "context": "", "use_case": "work tracking", "switched_from": "", "story": "AI promised less work. I've never worked more"}, {"id": 750474017, "item_id": 46904626, "url": "https://news.ycombinator.com/item?id=46904626", "by": "giancarlostoro", "date": "2026-02-05", "stance": "neutral", "quote": "I also made it so I can sync my tasks directly to my GitHub projects as well", "excerpt": "I was working on my own alternative to Beads... then I realized I could do exactly this with something similar to Beads, I'm planning on open sourcing it soon because I like what I have so far, I also made it so I can sync my tasks directly to my GitHub projects as well. I think its more useful to have agent tasks eventually synched back up to real ticketing systems for historical reasons. Besides, its better to have", "context": "", "use_case": "syncing agent tasks", "switched_from": "", "story": "Claude Code Agent Teams"}]}, {"text": " The main caveat is scale: it is recommended for teams of about four or fewer,", "cites": [{"id": 743302704, "item_id": 46456419, "url": "https://news.ycombinator.com/item?id=46456419", "by": "apothegm", "date": "2026-01-01", "stance": "recommend", "quote": "For tiny teams, Github Projects.", "excerpt": "For side projects, a TODO.md with Now, Next, Later, Maybe headings is usually perfect. I find that insufficient when there are non-technical tasks involved in a project, tho, and have yet to find a satisfactory solution. For tiny teams, Github Projects. For teams >4, Jira with streamlined kanban workflows and minimal bureaucracy.", "context": "", "use_case": "project management for tiny teams", "switched_from": "", "story": "Ask HN: What do you use to manage your coding projects?"}, {"id": 759394033, "item_id": 47462127, "url": "https://news.ycombinator.com/item?id=47462127", "by": "izajahmad", "date": "2026-03-20", "stance": "recommend", "quote": "For smaller projects I've gone back to a simple GitHub Projects board", "excerpt": "Linear for anything engineering-focused. The keyboard shortcuts and speed make a real difference when you're context-switching constantly. For smaller projects I've gone back to a simple GitHub Projects board \u2014 sometimes the overhead of dedicated PM tools isn't worth it when the team is under 5 people.", "context": "team under 5 people", "use_case": "small project tracking", "switched_from": "", "story": "Ask HN: Which one of the Pivotal Tracker successors do you use?"}]}, {"text": " with one commenter moving larger teams to Jira.", "cites": [{"id": 743302704, "item_id": 46456419, "url": "https://news.ycombinator.com/item?id=46456419", "by": "apothegm", "date": "2026-01-01", "stance": "recommend", "quote": "For tiny teams, Github Projects.", "excerpt": "For side projects, a TODO.md with Now, Next, Later, Maybe headings is usually perfect. I find that insufficient when there are non-technical tasks involved in a project, tho, and have yet to find a satisfactory solution. For tiny teams, Github Projects. For teams >4, Jira with streamlined kanban workflows and minimal bureaucracy.", "context": "", "use_case": "project management for tiny teams", "switched_from": "", "story": "Ask HN: What do you use to manage your coding projects?"}]}], "praise": [{"label": "AI agent tracking", "summary": "Commenters use it as the ticketing system that AI agents read, update and sync tasks into.", "quotes": [{"id": 776225553, "item_id": 48514097, "url": "https://news.ycombinator.com/item?id=48514097", "by": "yieldcrv", "date": "2026-06-12", "stance": "recommend", "quote": "My current process is also using Github projects in a normal scrum style way", "excerpt": "I don't know if I\u2019m overly critical but there\u2019s gotta be a middle ground between totally AI pilled people that otherwise have no talents, and control freak veteran developers who cant let go My current process is also using Github projects in a normal scrum style way, with many tickets written or fleshed out and state managed by the LLM, and it doubling as the memory system Completely leapfrogging all these other ope", "context": "", "use_case": "tickets and agent memory", "switched_from": "", "story": "Automating Myself Out of Development"}, {"id": 804174913, "item_id": 50260932, "url": "https://news.ycombinator.com/item?id=50260932", "by": "clord", "date": "2026-10-27", "stance": "neutral", "quote": "For work I use private GitHub project board", "excerpt": "I don\u2019t really use off the shelf agents. Usually just string together what I need. In this case I give the lead agent an mcp tool and tell it to use the service to track all work, and what should count and not. For work I use private GitHub project board and for personal stuff obsidian and markdown. I don\u2019t like big fat agents that try to do too much. Better to keep it lean, each agent prompt is really just a short b", "context": "", "use_case": "work tracking", "switched_from": "", "story": "AI promised less work. I've never worked more"}, {"id": 750474017, "item_id": 46904626, "url": "https://news.ycombinator.com/item?id=46904626", "by": "giancarlostoro", "date": "2026-02-05", "stance": "neutral", "quote": "I also made it so I can sync my tasks directly to my GitHub projects as well", "excerpt": "I was working on my own alternative to Beads... then I realized I could do exactly this with something similar to Beads, I'm planning on open sourcing it soon because I like what I have so far, I also made it so I can sync my tasks directly to my GitHub projects as well. I think its more useful to have agent tasks eventually synched back up to real ticketing systems for historical reasons. Besides, its better to have", "context": "", "use_case": "syncing agent tasks", "switched_from": "", "story": "Claude Code Agent Teams"}]}, {"label": "Simple kanban", "summary": "Its kanban board, including WIP limits, is described as working fine for real software teams.", "quotes": [{"id": 766559616, "item_id": 47909976, "url": "https://news.ycombinator.com/item?id=47909976", "by": "wpietri", "date": "2026-04-26", "stance": "recommend", "quote": "we use GitHub's kanban interface with WIP limits. That also works fine", "excerpt": "It has worked fine for me on a variety of software projects for more than 20 years. Here's a project I documented back in 2004, where we used physical cards: https://williampietri.com/writing/2004/teamroom/ These days I'm on an all-remote team, and we use GitHub's kanban interface with WIP limits. That also works fine, and them main difference form how I worked back then is that we no longer do estimates. I'm not sur", "context": "all-remote software team", "use_case": "team kanban board", "switched_from": "", "story": "I spent 6 years building my Kanban as I hated how managers run the boards"}, {"id": 776252992, "item_id": 48515812, "url": "https://news.ycombinator.com/item?id=48515812", "by": "hmokiguess", "date": "2026-06-13", "stance": "recommend", "quote": "I'm using GitHub issues and GitHub Projects with `gh` cli and I find it works well", "excerpt": "I'm using GitHub issues and GitHub Projects with `gh` cli and I find it works well, though what I really like about this is your project level chat. I find myself having to come back to a project level session often. May give this a try, just hesitant to put it on something that's in-flight with already lots of stuff, will have to be a net new project.", "context": "", "use_case": "task tracking", "switched_from": "", "story": "Show HN: Paca \u2013 Lightweight Jira alternative for human-AI collaboration"}, {"id": 776225553, "item_id": 48514097, "url": "https://news.ycombinator.com/item?id=48514097", "by": "yieldcrv", "date": "2026-06-12", "stance": "recommend", "quote": "My current process is also using Github projects in a normal scrum style way", "excerpt": "I don't know if I\u2019m overly critical but there\u2019s gotta be a middle ground between totally AI pilled people that otherwise have no talents, and control freak veteran developers who cant let go My current process is also using Github projects in a normal scrum style way, with many tickets written or fleshed out and state managed by the LLM, and it doubling as the memory system Completely leapfrogging all these other ope", "context": "", "use_case": "tickets and agent memory", "switched_from": "", "story": "Automating Myself Out of Development"}]}, {"label": "Low overhead", "summary": "Picked for small projects where dedicated PM tools feel like too much overhead.", "quotes": [{"id": 759394033, "item_id": 47462127, "url": "https://news.ycombinator.com/item?id=47462127", "by": "izajahmad", "date": "2026-03-20", "stance": "recommend", "quote": "For smaller projects I've gone back to a simple GitHub Projects board", "excerpt": "Linear for anything engineering-focused. The keyboard shortcuts and speed make a real difference when you're context-switching constantly. For smaller projects I've gone back to a simple GitHub Projects board \u2014 sometimes the overhead of dedicated PM tools isn't worth it when the team is under 5 people.", "context": "team under 5 people", "use_case": "small project tracking", "switched_from": "", "story": "Ask HN: Which one of the Pivotal Tracker successors do you use?"}, {"id": 743302704, "item_id": 46456419, "url": "https://news.ycombinator.com/item?id=46456419", "by": "apothegm", "date": "2026-01-01", "stance": "recommend", "quote": "For tiny teams, Github Projects.", "excerpt": "For side projects, a TODO.md with Now, Next, Later, Maybe headings is usually perfect. I find that insufficient when there are non-technical tasks involved in a project, tho, and have yet to find a satisfactory solution. For tiny teams, Github Projects. For teams >4, Jira with streamlined kanban workflows and minimal bureaucracy.", "context": "", "use_case": "project management for tiny teams", "switched_from": "", "story": "Ask HN: What do you use to manage your coding projects?"}]}], "caveats": [{"label": "Small teams only", "summary": "Recommended for teams under about five people, with larger teams moving to tools like Jira.", "quotes": [{"id": 743302704, "item_id": 46456419, "url": "https://news.ycombinator.com/item?id=46456419", "by": "apothegm", "date": "2026-01-01", "stance": "recommend", "quote": "For tiny teams, Github Projects.", "excerpt": "For side projects, a TODO.md with Now, Next, Later, Maybe headings is usually perfect. I find that insufficient when there are non-technical tasks involved in a project, tho, and have yet to find a satisfactory solution. For tiny teams, Github Projects. For teams >4, Jira with streamlined kanban workflows and minimal bureaucracy.", "context": "", "use_case": "project management for tiny teams", "switched_from": "", "story": "Ask HN: What do you use to manage your coding projects?"}, {"id": 759394033, "item_id": 47462127, "url": "https://news.ycombinator.com/item?id=47462127", "by": "izajahmad", "date": "2026-03-20", "stance": "recommend", "quote": "For smaller projects I've gone back to a simple GitHub Projects board", "excerpt": "Linear for anything engineering-focused. The keyboard shortcuts and speed make a real difference when you're context-switching constantly. For smaller projects I've gone back to a simple GitHub Projects board \u2014 sometimes the overhead of dedicated PM tools isn't worth it when the team is under 5 people.", "context": "team under 5 people", "use_case": "small project tracking", "switched_from": "", "story": "Ask HN: Which one of the Pivotal Tracker successors do you use?"}]}], "who": [{"by": "wpietri", "context": "all-remote software team", "url": "https://news.ycombinator.com/item?id=47909976", "date": "2026-04-26"}, {"by": "izajahmad", "context": "team under 5 people", "url": "https://news.ycombinator.com/item?id=47462127", "date": "2026-03-20"}], "tags": ["for small teams", "for AI agent workflows", "for remote teams", "for scrum"], "use_cases": ["work tracking", "task tracking", "tickets and agent memory", "team kanban board", "small project tracking", "syncing agent tasks"], "compared": [], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=50257325", "title": "AI promised less work. I've never worked more", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48515385", "title": "Show HN: Paca \u2013 Lightweight Jira alternative for human-AI collaboration", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48465890", "title": "Automating Myself Out of Development", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47877277", "title": "I spent 6 years building my Kanban as I hated how managers run the boards", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47452904", "title": "Ask HN: Which one of the Pivotal Tracker successors do you use?", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46902368", "title": "Claude Code Agent Teams", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {"recommend": 1}, "2026-02": {"neutral": 1}, "2026-03": {"recommend": 1}, "2026-04": {"recommend": 1}, "2026-05": {}, "2026-06": {"recommend": 2}, "2026-07": {}, "2026-08": {}, "2026-09": {}, "2026-10": {"neutral": 1}}, "quotes": [{"id": 804174913, "item_id": 50260932, "url": "https://news.ycombinator.com/item?id=50260932", "by": "clord", "date": "2026-10-27", "stance": "neutral", "quote": "For work I use private GitHub project board", "excerpt": "I don\u2019t really use off the shelf agents. Usually just string together what I need. In this case I give the lead agent an mcp tool and tell it to use the service to track all work, and what should count and not. For work I use private GitHub project board and for personal stuff obsidian and markdown. I don\u2019t like big fat agents that try to do too much. Better to keep it lean, each agent prompt is really just a short b", "context": "", "use_case": "work tracking", "switched_from": "", "story": "AI promised less work. I've never worked more"}, {"id": 776252992, "item_id": 48515812, "url": "https://news.ycombinator.com/item?id=48515812", "by": "hmokiguess", "date": "2026-06-13", "stance": "recommend", "quote": "I'm using GitHub issues and GitHub Projects with `gh` cli and I find it works well", "excerpt": "I'm using GitHub issues and GitHub Projects with `gh` cli and I find it works well, though what I really like about this is your project level chat. I find myself having to come back to a project level session often. May give this a try, just hesitant to put it on something that's in-flight with already lots of stuff, will have to be a net new project.", "context": "", "use_case": "task tracking", "switched_from": "", "story": "Show HN: Paca \u2013 Lightweight Jira alternative for human-AI collaboration"}, {"id": 776225553, "item_id": 48514097, "url": "https://news.ycombinator.com/item?id=48514097", "by": "yieldcrv", "date": "2026-06-12", "stance": "recommend", "quote": "My current process is also using Github projects in a normal scrum style way", "excerpt": "I don't know if I\u2019m overly critical but there\u2019s gotta be a middle ground between totally AI pilled people that otherwise have no talents, and control freak veteran developers who cant let go My current process is also using Github projects in a normal scrum style way, with many tickets written or fleshed out and state managed by the LLM, and it doubling as the memory system Completely leapfrogging all these other ope", "context": "", "use_case": "tickets and agent memory", "switched_from": "", "story": "Automating Myself Out of Development"}, {"id": 766559616, "item_id": 47909976, "url": "https://news.ycombinator.com/item?id=47909976", "by": "wpietri", "date": "2026-04-26", "stance": "recommend", "quote": "we use GitHub's kanban interface with WIP limits. That also works fine", "excerpt": "It has worked fine for me on a variety of software projects for more than 20 years. Here's a project I documented back in 2004, where we used physical cards: https://williampietri.com/writing/2004/teamroom/ These days I'm on an all-remote team, and we use GitHub's kanban interface with WIP limits. That also works fine, and them main difference form how I worked back then is that we no longer do estimates. I'm not sur", "context": "all-remote software team", "use_case": "team kanban board", "switched_from": "", "story": "I spent 6 years building my Kanban as I hated how managers run the boards"}, {"id": 759394033, "item_id": 47462127, "url": "https://news.ycombinator.com/item?id=47462127", "by": "izajahmad", "date": "2026-03-20", "stance": "recommend", "quote": "For smaller projects I've gone back to a simple GitHub Projects board", "excerpt": "Linear for anything engineering-focused. The keyboard shortcuts and speed make a real difference when you're context-switching constantly. For smaller projects I've gone back to a simple GitHub Projects board \u2014 sometimes the overhead of dedicated PM tools isn't worth it when the team is under 5 people.", "context": "team under 5 people", "use_case": "small project tracking", "switched_from": "", "story": "Ask HN: Which one of the Pivotal Tracker successors do you use?"}, {"id": 750474017, "item_id": 46904626, "url": "https://news.ycombinator.com/item?id=46904626", "by": "giancarlostoro", "date": "2026-02-05", "stance": "neutral", "quote": "I also made it so I can sync my tasks directly to my GitHub projects as well", "excerpt": "I was working on my own alternative to Beads... then I realized I could do exactly this with something similar to Beads, I'm planning on open sourcing it soon because I like what I have so far, I also made it so I can sync my tasks directly to my GitHub projects as well. I think its more useful to have agent tasks eventually synched back up to real ticketing systems for historical reasons. Besides, its better to have", "context": "", "use_case": "syncing agent tasks", "switched_from": "", "story": "Claude Code Agent Teams"}, {"id": 743302704, "item_id": 46456419, "url": "https://news.ycombinator.com/item?id=46456419", "by": "apothegm", "date": "2026-01-01", "stance": "recommend", "quote": "For tiny teams, Github Projects.", "excerpt": "For side projects, a TODO.md with Now, Next, Later, Maybe headings is usually perfect. I find that insufficient when there are non-technical tasks involved in a project, tho, and have yet to find a satisfactory solution. For tiny teams, Github Projects. For teams >4, Jira with streamlined kanban workflows and minimal bureaucracy.", "context": "", "use_case": "project management for tiny teams", "switched_from": "", "story": "Ask HN: What do you use to manage your coding projects?"}]}