The BMAD Method is an AI-assisted software development framework that provides a modular set of skills (workflows) to guide AI agents and humans through the entire development lifecycle. Each skill is a self-contained unit that can be invoked to perform specific tasks such as brainstorming, creating product requirements, designing architecture, implementing features, reviewing code, and conducting retrospectives. The framework maintains project context in `AGENTS.md` to ensure AI alignment with project-specific rules and supports deep customization via layered TOML configuration. Built for integration with AI-powered IDEs (like Claude Code, Cursor), the system emphasizes evidence-based practices, including validation lenses, memlog-based session tracking, and ticketing integration for work tracking. It also offers web bundle exports for deploying skills as Gemini Gems or ChatGPT Custom GPTs. The architecture features a clean separation of concerns, with skills encapsulating their own documentation, scripts, assets, and tests, while shared utilities handle configuration resolution, memlog logging, and validation. The project demonstrates strong engineering practices through automated validation tools, multi-language documentation, and a structured release process. While it manages complexity through modularity, users should be aware of maintenance risks such as duplicated validation text across skills and the need to place customizations in override directories to prevent loss during updates. Overall, the BMAD Method provides a robust, reusable toolkit for teams seeking to institutionalize AI-assisted development workflows.
Thunderdome Planning Poker is a full-stack web application for agile team collaboration that provides planning poker sessions, retrospectives, story mapping/storyboards, team check-ins, and project management capabilities. The application features a modular Go backend with clean separation of concerns (HTTP handlers, service layer, data access) and a Svelte-based frontend with TypeScript. It includes real-time collaboration via WebSockets, multiple authentication methods (local, LDAP, OIDC, header-based), subscription/billing with Stripe integration, and comprehensive API coverage. The system demonstrates sophisticated technical solutions including a fractional indexing system for maintaining ordered lists and a robust WebSocket hub implementation for real-time features.
jira.js is a comprehensive TypeScript SDK for Atlassian Jira REST APIs, covering Cloud, Data Center, Agile, Service Management, Assets, Administration, Teams, User Management, and User Provisioning surfaces. It is designed as a modular library with separate client factories (e.g., createCloudClient, createServerClient, createAgileClient) that provide typed access to hundreds of API endpoints. The architecture is built on a core transport layer that handles authentication (basic, bearer, OAuth 2.0), request/response validation using Zod schemas, error classification, retry logic, and multipart form data. Every API response is validated at runtime, with configurable behavior on schema mismatch (warn, throw, silent) and an optional audit mode to detect API drift. The library is primarily generated from Atlassian's OpenAPI specifications, resulting in a large, consistent codebase with models, parameters, and API functions organized by product domain. Key entry points include the client factories and subpath imports like 'jira.js/cloud' or 'jira.js/agile'. Data flows are straightforward: consumers construct typed request options and call client.sendRequest(), which returns validated response objects. External dependencies are minimal: zod for runtime validation, and the platform's fetch API for HTTP. The library also includes webhook signature verification, OAuth 2.0 (3LO) helpers for both Cloud and Data Center, and a browser-compatible bundle. Notable patterns include the use of apiObject and openEnum helpers to create Zod schemas that are permissive by default but strict under audit, enabling graceful handling of API evolution. The error hierarchy uses branded symbols for reliable type guards across package copies. The test suite includes extensive live integration tests against real Atlassian instances, with resource tracking and entitlement-aware gating. Overall, jira.js is a well-engineered, actively maintained SDK that prioritizes type safety and runtime validation, though its large generated surface introduces some duplication and maintenance overhead.
This repository is a comprehensively governed, production-grade library of 115+ prompt templates, meta-prompt generators, workshop guides, and structured routines for AI-assisted product management. It is not a deployed software application but rather a content methodology repository with application-like engineering discipline: standalone prompt contracts, coupling levels, CI-validated metadata, deterministic catalog generation, and an explicit coupling remediation plan. The library covers the full product management lifecycle—discovery, strategy, requirements, competitive intelligence, end-of-life, storytelling, and team facilitation—using three defined interaction modes (facilitation, co-construction, autonomous investigation). Notable sub-collections include an eight-discipline market intelligence framework (OSINT, FININT, GEOINT, etc.) with an all-source fusion prompt, a complete product sunset (EOL) workflow, and a TAM-SAM-SOM market sizing Langflow pipeline. The repo exhibits hybrid character: while primarily a content asset, it includes reusable Python scripts for validation and catalog generation, a GitHub Actions CI pipeline, and follows software engineering best practices such as versioning, changelogs, and architectural decision records.
Kanboard is a self-hosted, open-source project management application implementing the Kanban methodology. It provides a full web interface for managing tasks, projects, columns, swimlanes, subtasks, comments, tags, and time tracking, with drag-and-drop board interaction, automatic actions triggered by events, and extensive filtering/search capabilities. The architecture follows a custom MVC pattern with PHP controllers, models, and templates, using Pimple for dependency injection, PicoDb for database abstraction (supporting SQLite, MySQL, PostgreSQL, and MSSQL), and Symfony EventDispatcher for event-driven workflows. It includes a JSON-RPC API, CLI console commands, a plugin system, multiple authentication backends (LDAP, OAuth2, reverse proxy, TOTP), email notifications via SwiftMailer, and analytics (burndown, cumulative flow, lead/cycle time). The frontend uses jQuery and custom JavaScript components with charting via C3.js/D3.js. The codebase is well-structured with clear separation of concerns, extensive unit and integration tests, and a modular design that allows plugins to extend functionality. However, it is explicitly in maintenance mode (no new features, only bug fixes and community contributions), and several vendored libraries (SwiftMailer, PicoDb, JSON-RPC, etc.) may become outdated. The JavaScript layer relies on older patterns (jQuery, global namespace) and lacks a modern build pipeline. Configuration uses global constants rather than environment variables, and some areas show technical debt (e.g., mixed coding styles, deprecated PHP annotations). Despite these issues, the core architecture is solid, and many components (filter system, plugin installer, OAuth2 client, LDAP client, queue manager) are well-designed and potentially reusable in other PHP projects.