Task library CLSP
Project scope 10 tickets / 3 phases
Total focused work estimate 24h 45m + setup
Suggested stack TypeScript · JSON-RPC · Local protocol adapter · Vitest 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 CLSP-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice protocol ordering and document-safe editing.
What the team gains Inspect whether editor assistance preserves current user text and file boundaries.
Before you start Define the supported protocol subset and configuration grammar. Create synthetic open/change/close messages and workspace fixtures. Delivery agreement Test through local protocol messages; editor marketplace publishing is excluded.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Validate lifecycle and positions.
PHASE 2 Return current diagnostics and bounded edits.
PHASE 3 Cancel stale work and recover protocol errors.
Own document state Validate lifecycle and positions.
CLSP-101 Entry ticket; project setup still required Estimated field mix
Compiler and language tooling 80% API design 20% CLSP-102 Depends on CLSP-101 Estimated field mix
Compiler and language tooling 100% CLSP-103 Depends on CLSP-101, CLSP-102 Estimated field mix
Compiler and language tooling 100% Provide scoped assistance Return current diagnostics and bounded edits.
CLSP-104 Depends on CLSP-103 Estimated field mix
Compiler and language tooling 100% CLSP-105 Depends on CLSP-102, CLSP-103 Estimated field mix
Compiler and language tooling 100% CLSP-106 Depends on CLSP-103, CLSP-105 Estimated field mix
Compiler and language tooling 100% CLSP-107 Depends on CLSP-104, CLSP-106 Estimated field mix
Compiler and language tooling 70% API design 30% Handle client interruption Cancel stale work and recover protocol errors.
CLSP-108 Depends on CLSP-104, CLSP-107 Estimated field mix
Compiler and language tooling 60% Performance engineering 40% CLSP-109 Depends on CLSP-101, CLSP-108 Estimated field mix
Compiler and language tooling 60% Security 40% CLSP-110 Depends on CLSP-107, CLSP-109 Estimated field mix
Quality engineering 60% Compiler and language tooling 40% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.