ROADMAP

Last updated: 2026-05-19

Current State

What works:

• Complete 6-week onboarding plan with agentic tools, review pipelines, project management artifacts, issue mappings, student assignment strategy, and LLM/tooling usage progression (STUDENT_ONBOARDING_PLAN.md, restructured per DEC-004/005/006)
• 14 scaffolded student guides covering environment setup through agentic workflow best practices (docs/guides/)
• Templates for FEAST repos: CLAUDE.md, CONTRIBUTING.md, ADR template, vision plan template (templates/)
• Annotated reference bibliography with pedagogical and domain sources (references/)
• GitHub issue and PR templates (.github/)
• Project management scaffold: CLAUDE.md, ROADMAP.md, DECISIONS.md, post-commit hook
• Week 1 slide deck (58 sections: orientation, domain, architecture, agentic tools, setup, experience baseline, vision plan, plan comparison)
• Week 2 slide deck (28+ slides: review pipeline, git workflow, edge cases, iterative coding, ADRs, assigned work)
• Week 1 assignment document for senior developers (docs/assignments/week-1-assignment.md)
• Vision and Improvement Plan template (templates/vision-plan-template.md)
• Instructor prep guide for Week 2 LLM digest workflow (docs/instructor-guides/week-2-prep.md)
• Cohort org fork pattern with [COHORT-ORG] placeholder across curriculum, guides, and templates
• README with instructor setup instructions
• GitHub Pages deployment via GitHub Actions

In progress:

• Slide decks for weeks 3-6

Not started:

• Consistency review across all written materials
• Packaging guidance for reuse in other domains

Open questions:

• How much slide content should duplicate vs. reference the onboarding plan?
• What level of FEAST-environment readiness is needed before the first cohort starts?
• What agentic tool access will students have via GitHub educational accounts? (Affects Week 1 setup scaffold)

Milestones

M1: Core Curriculum [In Progress]

Goal: All written instructional materials are complete, consistent, and reviewed.

• Master onboarding plan (STUDENT_ONBOARDING_PLAN.md)
• Scaffolded student guides (docs/guides/01 through 09)
• FEAST repo templates (templates/)
• Reference bibliography (references/README.md)
• GitHub issue and PR templates (.github/)
• Curriculum restructuring (DEC-004): Integrate agentic tools, review pipelines, and project management artifacts
  • Week 1: Expand LLM tools section (tool landscape, CLAUDE.md as config, Claude Code setup), add project mgmt artifacts seed, add CLAUDE.md creation to solo work
  • Week 2: Add review pipeline intro, reorder linting scaffold to prioritize CI, introduce ADRs, require peer review on Week 2 PRs
  • Week 3: Add manual LLM review rotation, require ADR-format specs for more assigned work
  • Week 4: Reframe as “manual vs. auto-generated artifacts,” add ADR generation from diffs demo
  • Week 5: Add review pipeline retrospective and CLAUDE.md audit
  • Week 6: Add tool config handoff and process retrospective to handoff document
  • Update LLM Usage Progression table
  • Update Issue-to-Week Mapping Summary table
• Update CONTENT_MAP.md to reflect curriculum changes (slide impact per week)
• Curriculum additions (DEC-005): Deployment configuration mental model, Claude Code planning workflows, agentic engineering framing
  • Week 1: Deployment topology diagram, configuration matrix, three configuration levers
  • Week 2: /plan preview in iterative code pattern demo
  • Week 3: /plan for single-feature spec cross-checking, scaffold updates for #47 and #74
  • Week 4: /plan vs. /ultraplan vs. /ultrareview section, reporting feature scaffold update
  • Week 5: Deployment configuration audit exercise, /ultrareview in retrospective, security checklist update
  • Week 1: “Agentic engineering vs. vibe coding” framing section, Week 2 callback, Week 6 retrospective questions, success criteria updates
  • Update LLM Usage Progression table and Issue-to-Week Mapping Summary
  • Update CONTENT_MAP.md with new deployment and planning content
  • Fix environment setup guide (01) for consistency with curriculum (run_local.py, port 8000, client.js)
  • New guides: 10-deployment-configuration.md, 11-planning-with-claude-code.md
• Curriculum additions (DEC-006): Vision plans, cohort org fork, agent-assisted triage, plan comparison
  • Five-piece agent model and two-layer harness concept (curriculum, slides, guides 12-13)
  • Vision and Improvement Plan homework (Week 1 solo work restructure, template)
  • Cohort org fork pattern ([COHORT-ORG] across curriculum, guides, templates)
  • Agent-assisted issue triage (area labels, CLAUDE.md encoding, Plan Comparison Activity)
  • Week 1 assignment document (docs/assignments/week-1-assignment.md)
  • Instructor prep guide: LLM digest workflow (docs/instructor-guides/week-2-prep.md)
• Consistency review across all written materials (cross-references, terminology, scaffolding tiers)
• Verify FEAST code references (file paths, line numbers) against current codebase state

M2: Presentation Materials [In Progress]

Goal: Slide decks ready for all weekly group sessions.

• Week 1: Orientation, domain concepts, architecture, LLM tools intro (slides/week-1/)
• Week 1 update: Expand LLM tools slides (tool landscape, CLAUDE.md, Claude Code demo), add project mgmt artifacts slide, add Claude Code to setup slides
• Week 1 update: Experience baseline (01b), vision plan (38c), plan comparison (42), area labels in issue filing (39)
• Week 2: Review pipelines, CI setup, ADR introduction, edge case brainstorming, PR workflow (slides/week-2/)
• Week 2 update: Add vision plan recap card, assignment digest slide (02b)
• Week 3: Adversarial review (manual + LLM rotation), specs before code, ADR practice
• Week 4: Manual vs. auto-generated artifacts, roadmap maintenance, ADR generation from diffs
• Week 5: Security review, deployment readiness, review pipeline retrospective
• Week 6: Retrospective and handoff (may be discussion-driven, slides optional)

M3: Repo Scaffold [Complete]

Goal: This repo demonstrates the lightweight project management pattern it teaches.

• CLAUDE.md with project overview, workflow, and roadmap maintenance rules
• ROADMAP.md with milestones, dependency graph, and critical path
• DECISIONS.md seeded with foundational curriculum design decisions
• Post-commit hook for roadmap update reminders

M4: Pilot Readiness [Not Started]

Goal: Everything an instructor needs to run the first cohort, end to end.

• README.md with instructor setup instructions
• Pre-session LLM digest workflow for reviewing student submissions (docs/instructor-guides/week-2-prep.md)
• Pre-session checklists for remaining weeks
• Cohort GitHub org created and repos forked
• Verify FEAST backend/frontend repos are in expected state for student onboarding
• All materials reviewed by at least one other instructor or peer
• Dry-run of Week 1 session flow

M5: Post-Pilot Iteration [Not Started]

Goal: Incorporate feedback from the first cohort run.

• Collect student feedback (what worked, what was confusing, what was missing)
• Collect instructor observations (pacing, scaffolding levels, actual LLM usage patterns observed)
• Update guides based on common stumbling points
• Update onboarding plan based on actual vs. planned pacing
• Document deviations from plan and rationale

M6: Reusable Template [Not Started]

Goal: Package the pattern so others can adapt it for different projects and domains.

• Separate domain-specific content (FEAST, food access, Mesa) from domain-agnostic structure
• Write adaptation guide: how to create an onboarding program for a different project
• Document which pieces are FEAST-specific vs. reusable scaffolding
• Create a template branch or repo with placeholders where domain content goes

Dependency Graph

M1 (Core Curriculum)
 |
 +------> M2 (Presentations) -------+
 |                                   |
 +------> M3 (Repo Scaffold) -------+--> M4 (Pilot Readiness)
                                              |
                                              v
                                        M5 (Post-Pilot Iteration)
                                              |
                                              v
                                        M6 (Reusable Template)

M1 feeds M2 (slides reference the written curriculum) and M3 (repo scaffold needs to know the scope). M2 and M3 both feed M4 (pilot needs slides and a functioning repo pattern). M4 blocks M5 (must run the pilot to get feedback). M5 blocks M6 (must iterate before packaging as a template).

Critical Path to MVP (Pilot-Ready)

M1 (finish consistency review) -> M2 (at minimum, Week 1 slides) -> M4 (instructor prep + dry-run)

The minimum viable pilot requires: the onboarding plan, guides, Week 1 slides, and a working FEAST environment for students. Weeks 2-6 slides can be created just-in-time during the pilot if needed, but Week 1 must be complete before students arrive. M3 is already done.