Skip to main content
  • Pricing
Tutorials

GitHub Spec Kit: From Requirements to Tasks

By Oakgen TeamPublished 1 min read

Share
GitHub Spec Kit: From Requirements to Tasks

GitHub Spec Kit organizes work around a specification, a plan, and tasks that can be implemented and verified. Use the stages to make decisions explicit before asking an assistant to change a codebase.

Start with a behavior you can test

For an invoice export, specify who may export, which dates are included, and what an empty result means. Those are user-visible decisions. Leave the route, library and cache choices for the implementation plan unless the project already has a constraint in those areas.

In the plan, map each behavior to the systems that already own it. For this example, trace authorization to the current billing access check and date boundaries to the existing reporting convention. Keep assumptions visible, especially when a date format or timezone can alter the result.

Write tasks that finish with evidence

A useful task has an outcome and a way to verify it. One task might generate a CSV from existing invoice records and verify that the first and last dates match the filter. Another can prove that a signed-in user cannot export another account's invoices.

Review the tasks before implementation. If two work items could change the same behavior in incompatible ways, sequence them or clarify the contract first. The spec should still make sense to someone reading it without the implementation plan.

Continue with Oakgen Agent

Open in Oakgen Agent

Review the prefilled prompt before sending.

Open in Oakgen Agent

Sources

  1. GitHub, Spec Kit repository
Share