Projectquestorg Agileflow
AgileFlow is a Claude Code plugin for the Build phase that applies a framework-agnostic agile system—Scrum, Kanban, ADRs, and docs-as-code—for AI-assisted delivery.
by projectquestorg · github.com/projectquestorg/AgileFlow
Run AI-assisted agile delivery—epics, stories, Kanban, Scrum, and ADRs with docs-as-code—inside Claude Code, Cursor, or Windsurf without locking to one framework.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install projectquestorg-agileflow@projectquestorg/AgileFlowBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:projectquestorg/AgileFlow") and the paste-ready config with skillselion.get_install_config("plugin:projectquestorg/AgileFlow").
What it does
Projectquestorg AgileFlow is a community Claude Code plugin that packages AI-driven agile practices for builders who want structure without adopting a heavyweight enterprise toolchain. It merges Scrum and Kanban flow with architecture decision records and docs-as-code so requirements, status, and technical choices live beside the code your agent edits. Solo founders use it to keep epics and stories honest while agents implement features, and to document why decisions were made before memory fades. Because it is methodology-heavy, it pays off across Validate scoping, Build execution, and Ship readiness even though the catalog shelf is Build PM. It is not a replacement for issue trackers or CI; it is the conversational command layer for agile ceremonies and documentation. Expect one plugin in the bundle and vocabulary oriented toward automation, collaboration, and multi-agent research.
Highlights
- Framework-agnostic agile system combining Scrum, Kanban, ADRs, and docs-as-code
- Multi-agent collaboration keywords: epics, features, stories, and research-oriented commands
- Universal across Claude Code, Cursor, Windsurf, and similar coding agents
- AgileDocs-as-code style automation for managing decisions and delivery docs in-repo
Why builders use it
Agent-assisted coding without agile structure creates orphaned features, missing ADRs, and docs that never stay in sync with what shipped.
After install, you can drive epics, stories, kanban flow, and in-repo decision docs through consistent commands so agents and humans share the same delivery narrative.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 7 stars, 0 votes.
FAQ
Who is projectquestorg-agileflow for?
Indie and small teams who want AI-driven agile ceremonies, backlog language, and docs-as-code while coding in Claude Code, Cursor, or Windsurf.
When should I use projectquestorg-agileflow?
Use it when you are shaping work into epics and stories, recording ADRs, and keeping delivery docs current—especially during Build and when preparing Ship-ready increments.
How do I add projectquestorg-agileflow to my agent?
Register the AgileFlow plugin from projectquestorg/AgileFlow in your agent’s plugin UI, then anchor your repo with docs-as-code folders and invoke its agile commands during planning and implementation sessions.
Comments
Share how you use projectquestorg-agileflow, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.