Task library BSDKGEN Developer tooling · Phased project Deterministic SDK publishing pipeline A fictional partner platform publishes TypeScript clients. Generator upgrades create noisy diffs, occasional runtime mismatches, and uncertainty about which schema was packaged.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 29h + setup
Suggested stack TypeScript · OpenAPI · Node.js 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 BSDKGEN-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice reproducible generation, compatibility reviews, and package provenance.
What the team gains Reduce partner integration surprises with reviewable clients and recoverable releases.
Before you start Create a small public API schema and two local mock server versions; use a temporary local package registry or archive files. Delivery agreement Deliver the local generation and packaging workflow with a compatibility report; publish nothing externally.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Specify schema and generator provenance.
PHASE 2 Produce usable stable clients and visible changes.
PHASE 3 Exercise installation, compatibility, and recovery locally.
Pin inputs Specify schema and generator provenance.
BSDKGEN-101 Entry ticket; project setup still required BSDKGEN-102 Depends on BSDKGEN-101 Estimated field mix
Developer tooling 60% API design 40% Generate predictably Produce usable stable clients and visible changes.
BSDKGEN-103 Depends on BSDKGEN-102 Estimated field mix
Developer tooling 50% API design 30% Networking 20% BSDKGEN-104 Depends on BSDKGEN-103 Estimated field mix
Developer tooling 60% API design 40% BSDKGEN-105 Depends on BSDKGEN-103 Estimated field mix
API design 50% Developer tooling 30% Security 20% BSDKGEN-106 Depends on BSDKGEN-102 Estimated field mix
API design 60% Developer tooling 40% Verify packages Exercise installation, compatibility, and recovery locally.
BSDKGEN-107 Depends on BSDKGEN-104, BSDKGEN-105 Estimated field mix
Developer tooling 70% Quality engineering 30% BSDKGEN-108 Depends on BSDKGEN-107 Estimated field mix
Developer tooling 80% Quality engineering 20% BSDKGEN-109 Depends on BSDKGEN-106, BSDKGEN-107 Estimated field mix
Developer tooling 40% API design 30% Quality engineering 30% BSDKGEN-110 Depends on BSDKGEN-109 Estimated field mix
Developer tooling 60% Platform engineering 40% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.