A scaffold is a temporary, partial implementation that establishes structure without pretending the behavior is finished. It shortens the gap between a decision and a runnable starting point while keeping product decisions with the developer. section 3.2.1 section 3.1.2
Start with an explicit contract, then constrain the work to setup: files, wiring, a handler skeleton, or test structure. Mark missing behavior visibly. A stub that runs is useful; a plausible-looking implementation that invents requirements creates work to undo. section 3.2 section 3.2.1 section 3.6
An endpoint that is deliberately unfinished
An API contract calls for 200 when an order is found and 404 when it is not. A constrained prompt asks for a minimal handler from ./api.yaml, with TODOs for those cases, no validation or business logic, and a temporary 501 response. The 501 tells callers the endpoint is not implemented; it is not a new contract requirement. section 3.2.1
Listing 3.1 Handler skeleton with no design decisions
export async function getOrder(req: Request, res: Response) {
// TODO: Implement order retrieval logic
// TODO: Handle 404 case when order not found
res.status(501).json({ error: "Not implemented" });
}
The handler skeleton shows TODOs for retrieval and the 404 case while returning 501 until the contract-defined behavior is implemented. section 3.2.1
Keep the scaffold easy to replace. Ask whether it exposes the next decision and speeds feedback, or merely makes unfinished work look complete. Review it against the contract, not just whether it compiles. section 3.0 section 3.1.2 section 3.6



