A project is six topics

Claim: a project is a folder of six parts, problem, scope, review, baseline, plan and trail, each written as a topic.

Grade: convention, untested; an outline raised judged writing quality in an experiment (Kellogg 1988, secondary), and a plan written as a topic is not tested.
Evidence: position; review, answers to the four questions; decision 0003; Peffers 2006; Kellogg 1988 (secondary).
Check: project-shape (errors, warnings): each project root that declares the shape has its six parts, each part announces the topic shape and holds its own required rows or headings.
Reader styles: none.

What it asks

Declare the project shape on a line labelled Shape: in the root.
Write each part as a topic: a title, a summary, then the body, with the topic shape announced.
Keep to the six parts; a job that needs fewer is not a project in this sense.

The parts follow the activities of the design science process from problem to evaluation (Peffers 2006), with the review and the baseline made steps of their own.
A part with its own rows or headings can be checked by a program, so a missing part is an error and not a matter of taste.

Six parts is a convention, and may cost a small job more than it saves (decision 0003).
The shape ends where the genres begin: a document the project produces keeps the shape of its genre.