AI-Powered Development Workflow Platform
APDevFlow is a lightweight scrum dashboard and AI-powered development workflow accelerator that helps Product Owners break down features into epics and stories, and helps developers generate implementation specs using AI skills.
Created by: Aaron Prill (@prillcode) Status: Planning Phase License: TBD
This is a pnpm + Turborepo monorepo. Follow these steps to get started:
Ensure you have the following installed:
- Node.js >= 20.0.0
- pnpm >= 9.0.0
# Install pnpm if needed
npm install -g pnpm@9.0.0
# Verify versions
node --version # Should be >= 20
pnpm --version # Should be >= 9git clone https://github.com/prillcode/apdevflow.git
cd apdevflow# Install all dependencies for all packages
pnpm installThis will install dependencies for:
- Root workspace
apps/web(React dashboard)apps/api(Lambda functions)apps/cli(devflow CLI)packages/shared(shared types/utils)packages/skills-adapter(skill API adaptation)
# Build everything in parallel with Turborepo
pnpm build
# Or build specific packages
pnpm --filter @apdevflow/shared build
pnpm --filter @apdevflow/cli buildThe repository contains Claude Code skills that need to be symlinked to your local Claude skills directory:
# Create skills directory if it doesn't exist
mkdir -p ~/.claude/skills
# Create symlinks (adjust path to match where you cloned the repo)
REPO_PATH="$PWD" # Or use absolute path like ~/projects/apdevflow
ln -s "$REPO_PATH/skills/api-skills/epic-feature-creator" ~/.claude/skills/epic-feature-creator
ln -s "$REPO_PATH/skills/api-skills/feature-story-creator" ~/.claude/skills/feature-story-creator
ln -s "$REPO_PATH/skills/local-skills/dev-orchestrator" ~/.claude/skills/dev-orchestrator
ln -s "$REPO_PATH/skills/local-skills/dev-spec" ~/.claude/skills/dev-spec
ln -s "$REPO_PATH/skills/local-skills/dev-execute" ~/.claude/skills/dev-execute
ln -s "$REPO_PATH/skills/local-skills/git-commit-helper" ~/.claude/skills/git-commit-helper
ln -s "$REPO_PATH/skills/local-skills/debug-like-expert" ~/.claude/skills/debug-like-expert# Check that symlinks are created
ls -la ~/.claude/skills/ | grep apdevflow
# Check that builds succeeded
ls -la apps/cli/dist
ls -la packages/shared/dist
# Test CLI (after build)
node apps/cli/dist/cli.js --version# Start development mode (watches for changes)
pnpm dev
# Run web app only
pnpm --filter @apdevflow/web dev
# Run CLI in dev mode
pnpm --filter @apdevflow/cli dev
# Adapt API skills (regenerate api-prompt.md files)
pnpm adapt-skills# Run builds
pnpm build # Build all packages
# Clean everything
pnpm clean # Remove dist/ and node_modules
# Format code
pnpm format # Run Prettier
# Lint code
pnpm lint # Run ESLint
# Run tests
pnpm test # Run all testsThat's it! The monorepo is set up and ready for development. π
- Product Requirements Document (Revised) - Complete PRD with architecture, workflows, and MVP phases
- Original PRD - Initial planning document (for reference)
- Deployment Guide - Self-hosted deployment options and setup instructions
- GitHub OAuth Setup - Complete guide to setting up GitHub OAuth integration
- Claude Integration Strategy - Deep dive on Claude Code vs. Claude API approaches
- Git Worktrees Integration - Developer workflow with git worktrees
- Branding Guide - Brand identity and naming conventions
- Skills Reference - How APDevFlow uses Claude Code skills
APDevFlow is NOT just another JIRA plugin. It's a standalone workflow tool that:
- π AI-Powered Planning - Paste a feature request or PRD, get AI-generated epics and user stories
- β Review & Approve - Edit AI output before creating tickets
- π€ Flexible Export - Export to JIRA (CSV for MVP, API later), Linear, or use standalone
- π Fast Spec Generation - Export story to workspace, use Claude Code skills to generate implementation specs
- πΏ Git Worktree Integration - One worktree per story for clean separation
- π¦ Artifact Management - Track all generated specs and code with versioning
- β±οΈ 70% faster spec writing (45 min β 5 min)
- π 15x faster epic breakdown (3 hours β 15 min)
- π° Low cost - $25-30/month for entire team
- π Not locked-in - Works with or without JIRA
GitHub Spec Kit is an excellent CLI tool for spec-driven development. While there's overlap in spec generation, APDevFlow serves a fundamentally different purpose:
| Aspect | GitHub Spec Kit | APDevFlow |
|---|---|---|
| What it does | Generate specs before coding | Full workflow orchestration |
| Target user | Individual developers | Product Owners + Dev Teams |
| Scope | Pre-implementation specs | Idea β Planning β Code β Artifacts |
| Architecture | CLI tool (Python) | Web Dashboard + API + DB + CLI |
| Team features | β Solo-focused | β Collaboration & assignment |
| Project management | β None | β Planning dashboard, tracking |
| Self-hosted | β Yes | β Yes (full infrastructure) |
The key difference: Spec Kit is a tool for better specs. APDevFlow is a platform for team coordination.
Can they work together? Yes! APDevFlow can optionally integrate Spec Kit as a spec generation engine while providing the team collaboration, planning dashboard, and artifact management layers.
Think of it as:
- Spec Kit = Prettier (excellent code formatter)
- APDevFlow = VSCode (full IDE that can use Prettier)
See Competitive Differentiation for detailed comparison.
βββββββββββββββββββββββββββββββββββββββββββββββ
β APDevFlow Platform β
βββββββββββββββββββββββββββββββββββββββββββββββ€
β β
β π± Planning Dashboard (React SPA) β
β - Feature β Epic β Story breakdown β
β - AI-powered generation via Bedrock β
β - Review/edit/approve workflow β
β β
β π» Developer Dashboard (React SPA) β
β - My Stories view β
β - Artifact viewer β
β - Export to workspace β
β β
β π§ CLI Tool (devflow) β
β - devflow start story-123 β
β - devflow finish story-123 β
β - devflow skills install β
β β
β βοΈ Backend (Hono API) β
β - Pure Hono application β
β - Deploy anywhere: Lambda, Fly.io, β
β Railway, ECS, VPS, etc. β
β - DynamoDB (Features/Epics/Stories) β
β - S3 (artifacts, exports) β
β - Bedrock (Claude API for PO flows) β
β β
βββββββββββββββββββββββββββββββββββββββββββββββ
β
β
βββββββββββββββββββββββββ
β Claude Code Skills β
β (from claudeai-dev) β
βββββββββββββββββββββββββ
Frontend:
- React 18 + TypeScript
- Tailwind CSS + shadcn/ui
- TanStack Query
- Vite
Backend:
- Hono (lightweight web framework)
- Node.js 20.x
- Deployment options:
- AWS Lambda (serverless)
- Fly.io / Railway (PaaS)
- AWS ECS/Fargate (containers)
- VPS (DigitalOcean, Linode, etc.)
- DynamoDB / PostgreSQL / MySQL
- S3 (artifacts, exports)
- Bedrock (Claude API)
CLI:
- TypeScript (compiled to Node.js)
- Distributed via npm + Homebrew
APDevFlow includes Claude Code skills directly in this repository under skills/.
| Skill | Purpose | Mode | Location |
|---|---|---|---|
| epic-feature-creator | Break down feature β epics | Claude API (Bedrock) | skills/api-skills/ |
| feature-story-creator | Break down epic β stories | Claude API (Bedrock) | skills/api-skills/ |
| dev-orchestrator | Orchestrate full dev workflow | Claude Code (local) | skills/local-skills/ |
| dev-spec | Generate implementation specs | Claude Code (local) | skills/local-skills/ |
| dev-execute | Implement from spec | Claude Code (local) | skills/local-skills/ |
| git-commit-helper | Generate commit messages | Claude Code (local) | skills/local-skills/ |
| debug-like-expert | Deep debugging methodology | Claude Code (local) | skills/local-skills/ |
API Skills (skills/api-skills/)
- Invoked by backend Lambda functions via Claude API (Bedrock)
- Used in Planning Dashboard for PO workflows
- Each skill has
SKILL.md(full) andapi-prompt.md(API-adapted)
Local Skills (skills/local-skills/)
- Invoked by developers using Claude Code locally
- Symlinked to
~/.claude/skills/for immediate availability - Full tool access (Read, Write, Bash, Git, etc.)
Backend (API Skills):
// Lambda loads API-adapted prompt
const prompt = await fs.readFile(
'./skills/api-skills/epic-feature-creator/api-prompt.md'
);
// Invoke via Bedrock
const epics = await bedrock.invokeModel({
system: prompt,
messages: [{ role: 'user', content: featureDescription }]
});Local (Developer Skills):
# Developer uses Claude Code
cd ~/repos/myapp-story-123
claude-code
> Use dev-orchestrator to implement this story
# Claude Code loads ~/.claude/skills/dev-orchestrator/SKILL.mdSee skills/README.md for detailed documentation on skill development and usage.
- React dashboard with Tailwind + shadcn/ui
- Feature β Epic β Story generation via Bedrock
- Cognito authentication
- DynamoDB storage
- Developer "My Stories" view
- Story export to local workspace
- CLI tool basics (
devflow start,devflow list)
devflow finishuploads artifacts- Git worktree integration
- Artifact viewer in dashboard
- CSV export for JIRA bulk import
- Manual workflow (automated later)
devflow skills installautomation- User documentation
- Video walkthrough
- Usage analytics dashboard
- Error handling
- Production-ready
Total MVP: 10 weeks (~200 hours)
- Lambda: ~$1
- DynamoDB: ~$3-5
- S3: ~$1
- API Gateway: ~$0.25
- CloudFront: ~$5
- Bedrock Claude API: ~$11
- Secrets Manager: ~$2
- CloudWatch: ~$2
Total: $25-30/month for entire team
Per Developer (team of 20): $1.50/month
- Time saved per developer: ~8 hours/month
- Value: $50/hour (conservative)
- Monthly value: 20 devs Γ 8 hrs Γ $50 = $8,000
- Monthly cost: $30
- ROI: 26,600%
- Product Name: APDevFlow (AI-Powered DevFlow)
- CLI Command:
devflow(primary) +apdev(alias) - Brand Identity: "AP" = Agile Programming + Aaron Prill
- Tagline: "Where planning meets implementation, powered by AI"
- claudeai-dev - Reusable Claude Code skills library (required dependency)
- Claude Code - Official Anthropic CLI tool (developer prerequisite)
Phase: Early Development π
Completed:
- β Product Requirements Document (revised)
- β Architecture design
- β Integration strategy
- β Cost modeling
- β Skills identification
- β Planning Dashboard UI (localStorage-based)
- β GitHub OAuth integration (frontend + backend)
- β Monorepo setup with Turborepo
- β API refactored to pure Hono architecture
- β GitHub repository file path autocomplete
- β Deployment-agnostic backend (Lambda, Fly.io, Railway, VPS)
In Progress:
- π¨ DynamoDB schema design
- π¨ Bedrock integration for spec generation
- π¨ Deployment automation (IaC templates)
Next Steps:
- Complete database integration (DynamoDB/PostgreSQL)
- Add Bedrock integration for AI-powered planning
- Build developer dashboard
- Implement CLI tool
- Create deployment templates (AWS CDK, Docker Compose)
This project is currently in the planning phase. Contributions will be welcome once development begins.
License TBD (likely MIT or Apache 2.0)
Creator: Aaron Prill GitHub: @prillcode
Built with β€οΈ using Claude Code and AI-powered workflows