We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

• 0

  Common

  Most of the 16 edited versions we read keep these.

• 6

  Distinctive

  This author's own choices. Worth a look.

• 0

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Distinctive:

   Use for converting Notion specs into implementation plans, execution tasks, progress updates, and linked delivery artifacts.

   line 9
2. Distinctive:

   Create a plan page sized to the change: quick plan for small work, phased plan for multi-step features or migrations.

   line 14
3. Distinctive:

   Create linked tasks that are small enough to execute, verify, and assign cleanly.

   line 15
4. Distinctive:

   Keep the spec, plan, and tasks connected so later status updates can be traced back to the original requirements.

   line 16
5. Distinctive:

   Do not turn an ambiguous spec into tasks without surfacing the missing assumptions.

   line 23
6. Distinctive:

   Do not create oversized, vague tasks that cannot be verified independently.

   line 24

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.