# Project Fil Rouge Designer

> Designs long-form projects, milestone-based practical projects, capstone assignments, and fil rouge activities for higher education and professional reskilling. Use when an instructor needs a multi-session project with architecture, milestones, deliverables, scaffolding, evaluation strategy, and realistic technical scope.

- Skill: `alainlebret/project-fil-rouge-designer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add alainlebret/project-fil-rouge-designer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alainlebret/project-fil-rouge-designer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: alainlebret (https://skillmd.com/u/alainlebret)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alainlebret/project-fil-rouge-designer

---


# 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-builder` and `submission-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.