Task library BUILD Developer tooling · Phased project Make the monorepo feedback loop trustworthy A product team waits for every package to rebuild after small changes. An experimental cache is faster but occasionally returns success after a shared type changed. Build a small, auditable task runner around fixture packages.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 20h 45m + setup
Suggested stack TypeScript · Node.js · pnpm · JSON Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with BUILD-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice incremental computation, dependency scheduling, cache correctness, and cancellation.
What the team gains Inspect whether faster checks preserve the guarantees reviewers depend on.
Before you start Prepare four fixture packages with one shared library and two applications. Use only trusted fixture commands in local tests. Delivery agreement A dependency-aware check runner with a local cache and reproducible benchmark report.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Make task selection and scheduling predictable.
PHASE 2 Prove when outputs may safely be reused.
PHASE 3 Control resources and report failures without hiding them.
Model checks and dependencies Make task selection and scheduling predictable.
BUILD-101 Entry ticket; project setup still required Estimated field mix
Developer tooling 80% Security 20% BUILD-102 Depends on BUILD-101 BUILD-103 Depends on BUILD-101 Cache only valid results Prove when outputs may safely be reused.
BUILD-104 Depends on BUILD-102 Estimated field mix
Developer tooling 80% Storage systems 20% BUILD-105 Depends on BUILD-104 Estimated field mix
Security 50% Developer tooling 30% Storage systems 20% BUILD-106 Depends on BUILD-103, BUILD-104 Estimated field mix
Developer tooling 60% Storage systems 40% Make the runner usable in CI Control resources and report failures without hiding them.
BUILD-107 Depends on BUILD-103 BUILD-108 Depends on BUILD-103 Estimated field mix
Developer tooling 60% Performance engineering 40% BUILD-109 Depends on BUILD-104, BUILD-106 Estimated field mix
Developer tooling 70% Privacy engineering 30% BUILD-110 Depends on BUILD-105, BUILD-106, BUILD-107, BUILD-108, BUILD-109 Estimated field mix
Performance engineering 50% Developer tooling 30% Quality engineering 20% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.