github4farms

Research and catalog industry standards and frameworks applied to the project with citations, application mapping, and maturity model. Use alongside domain research to ground the project in established practice.

Create or update the version history following Keep a Changelog 1.1.0 format. Use as the final step after all artifacts are generated.

Analyze the work breakdown structure to identify critical path, parallel work opportunities, dependency chains, resource conflicts, and bottlenecks. Use after JIRA structure defines epics.

Research the problem domain to understand industry standards, terminology, regulatory requirements, and artifact expectations. Use when starting a new project or when industry context is needed for planning artifacts.

Generate an executive-ready slide deck as HTML slide sources with Node.js build scripts for PowerPoint assembly. Use as the final deliverable after all artifacts are complete.

Create a visual project timeline with SVG Gantt chart, Mermaid critical path diagram, dependency matrix, and milestone tracking. Use after JIRA structure and dependency analysis are complete.

Create visual project summary infographics for the README and GitHub social preview images with before/after comparison, ROI highlights, and phase timeline. Use after core artifacts are complete.

Generate a complete JIRA epic/story hierarchy with acceptance criteria, sprint planning, issue type taxonomy, labels, and team assignments. Use after project plan defines phases.

Conduct a structured interview to elicit project knowledge and produce a complete PROJECT-CONTEXT.md. Use when starting a new project or when PROJECT-CONTEXT.md needs to be created or refined.

Generate a comprehensive master project plan with executive summary, current state analysis, phased approach, financial ROI, and actionable next steps. Use after domain research is complete.

Create a responsibility assignment matrix mapping all project activities to roles with R/A/C/I designations including ongoing governance. Use after project plan and JIRA structure define activities and roles.

Generate a professional GitHub README with status badges, visual overview infographic, Mermaid diagrams, artifact navigation, team information, and timeline summary. Use as the final documentation step after all artifacts are complete.

Identify, assess, and plan mitigation for all project risks with likelihood/impact scoring, contingency plans, and monitoring schedules. Use after project plan defines scope and constraints.

Create a standardized operational runbook/playbook template with triage steps, diagnosis procedures, resolution scenarios, escalation paths, and an automation example. Use when the project involves operational procedures.

Define a severity/priority classification framework with decision criteria, routing rules, escalation procedures, and governance process. Use when the project involves operational processes, incidents, or work item triage.

Define comprehensive KPIs with measurement methods, baselines, targets, calculation formulas, dashboard specifications, and project closure criteria. Use after project plan defines goals.

Generate a programmatic SVG Gantt chart with phase-coded colors, task bars, sub-tasks, milestones, and dark-theme design. Use when creating or updating the visual timeline.