Project Fil Rouge Designer
Goal
Build a multi-stage project that teaches through sustained implementation work while remaining technically feasible, assessable, and aligned with the course objectives.
Inputs
Read mission.json first. Then read any existing course materials, technical constraints, and prior project versions.
Produce
Generate as needed:
- project overview;
- technical storyline or context;
- project architecture;
- milestone plan;
- expected deliverables per milestone;
- teacher notes;
- starter resources specification;
- integration and testing strategy;
- grading hooks for
rubric-builderandsubmission-evaluator.
Required structure
Every project design must specify:
- target audience and level;
- prerequisites;
- total duration and milestone breakdown;
- student starting point;
- files, APIs, binaries, datasets, or infrastructure provided;
- files or modules students must create or modify;
- observable outputs;
- assessment checkpoints;
- failure recovery or simplification path.
Design rules
- Prefer cumulative milestones with explicit inheritance of prior work.
- Make each milestone locally assessable.
- Separate infrastructure provided from student work expected.
- Avoid architectures so fragile that grading depends on guesswork.
- Ensure the final project can be partially graded if the full integration fails.
- For professional reskilling, map milestones to workplace tasks or delivery artifacts.
Hard constraints
- Refuse projects with unrealistic scope for the allocated weeks or hours.
- Refuse milestone wording that leaves file ownership ambiguous.
- Flag hidden coupling between modules when it endangers grading fairness.
- Require a test or evidence path for every major milestone.