Skip to content

prillcode/apdevflow

Repository files navigation

APDevFlow

AP_DevFlow_Logo_Clean

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


⚑ Quick Setup (New Machine)

This is a pnpm + Turborepo monorepo. Follow these steps to get started:

1. Prerequisites

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 >= 9

2. Clone the Repository

git clone https://github.com/prillcode/apdevflow.git
cd apdevflow

3. Install Dependencies

# Install all dependencies for all packages
pnpm install

This 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)

4. Build All Packages

# Build everything in parallel with Turborepo
pnpm build

# Or build specific packages
pnpm --filter @apdevflow/shared build
pnpm --filter @apdevflow/cli build

5. Setup Skills Symlinks

The 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

6. Verify Setup

# 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

7. Development Workflow

# 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

8. Useful Commands

# 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 tests

That's it! The monorepo is set up and ready for development. πŸš€


πŸ“š Documentation


🎯 What is APDevFlow?

APDevFlow is NOT just another JIRA plugin. It's a standalone workflow tool that:

For Product Owners

  • πŸ“ 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

For Developers

  • πŸš€ 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

Key Benefits

  • ⏱️ 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

πŸ” How APDevFlow Compares

vs. GitHub Spec Kit

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.


πŸ—οΈ Architecture Overview

Components

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚          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)  β”‚
        β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Technology Stack

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

🧩 Skills Integration

APDevFlow includes Claude Code skills directly in this repository under skills/.

Skills Included

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/

Skill Organization

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) and api-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.)

How Skills Work

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.md

See skills/README.md for detailed documentation on skill development and usage.


πŸš€ MVP Roadmap

Phase 1: Core Dashboard + AI Planning (Weeks 1-2)

  • React dashboard with Tailwind + shadcn/ui
  • Feature β†’ Epic β†’ Story generation via Bedrock
  • Cognito authentication
  • DynamoDB storage

Phase 2: Developer Dashboard + Story Export (Weeks 3-4)

  • Developer "My Stories" view
  • Story export to local workspace
  • CLI tool basics (devflow start, devflow list)

Phase 3: Artifact Upload + Git Worktrees (Weeks 5-6)

  • devflow finish uploads artifacts
  • Git worktree integration
  • Artifact viewer in dashboard

Phase 4: JIRA Integration (Week 7)

  • CSV export for JIRA bulk import
  • Manual workflow (automated later)

Phase 5: Skill Installation + Docs (Week 8)

  • devflow skills install automation
  • User documentation
  • Video walkthrough

Phase 6: Analytics + Polish (Weeks 9-10)

  • Usage analytics dashboard
  • Error handling
  • Production-ready

Total MVP: 10 weeks (~200 hours)


πŸ’° Cost Model

AWS Infrastructure (Monthly)

  • 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

ROI Calculation

  • 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%

🎨 Branding

  • 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"

πŸ”— Related Projects

  • claudeai-dev - Reusable Claude Code skills library (required dependency)
  • Claude Code - Official Anthropic CLI tool (developer prerequisite)

πŸ“‹ Current Status

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:

  1. Complete database integration (DynamoDB/PostgreSQL)
  2. Add Bedrock integration for AI-powered planning
  3. Build developer dashboard
  4. Implement CLI tool
  5. Create deployment templates (AWS CDK, Docker Compose)

🀝 Contributing

This project is currently in the planning phase. Contributions will be welcome once development begins.


πŸ“„ License

License TBD (likely MIT or Apache 2.0)


πŸ“§ Contact

Creator: Aaron Prill GitHub: @prillcode


Built with ❀️ using Claude Code and AI-powered workflows

About

APDevFlow is a lightweight scrum dashboard and AI-powered development workflow accelerator

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •