implementation-details

To generate a development checklist, the Skill reads your project contract file to determine your tech stack, tracker markup, and testing frameworks, then outputs a terse, imperative list of actionable work items for the ticket.

A technical implementation checklist defines actionable work items for a development ticket during the planning phase, ensuring developers cover code changes, automated tests, and manual QA steps without missing critical steps like linting or visual regression.

To ensure ticket planning includes project-specific QA steps, the Skill uses context-aware generation by reading your project contract to tailor the checklist to your specific stack, testing frameworks, and environment-specific QA requirements.

Yes, you need a project contract file to generate a dev checklist because the Skill requires access to it to determine tracker markup, testing frameworks, and environment-specific QA requirements for context-aware generation.

The best way to eliminate ambiguity in ticket planning is to generate a structured, project-specific technical implementation checklist that produces an action-oriented, terse list of work items rather than narrative descriptions or vague categories.

You can use this for any stack specified in your project contract file, as the Skill applies context-aware generation to tailor the checklist based on your project-specific stack, tracker markup, and environment details.