All libraries

1. Questions before the plan

   Use it when: A new feature has arrived and you want to know what is still unclear before you start planning.

   Works with any AI assistant.

   Fill in your parts

   FeatureFor example: task deadline reminders by email

   Short descriptionFor example: an email one day before a task deadline

   Module layoutFor example: the tasks module folder and file list

   Your prompt

   Goal: before planning ‹fitur›, I want to know what is unclear.
   Reader: me, the feature owner.
   Material: ‹deskripsi› and ‹struktur›.
   Limits: do not write the plan. Do not guess file or function names outside the material.
   Shape: at most eight questions, grouped product, data, technical.
   Check: name the risk if each question is answered with a wrong assumption.

   Copy prompt

   Learn it in: Prompts for plans and specifications

2. Feature plan

   Use it when: The feature requirements are clear enough and you need a written plan to review before any code exists.

   Works with any AI assistant.

   Fill in your parts

   FeatureFor example: task deadline reminders by email

   AnswersFor example: recipient: the assignee; time zone: WIB

   Module layoutFor example: the tasks module folder and file list

   Team rulesFor example: tests first, flags read in one function

   Your prompt

   Goal: I need a plan for ‹fitur›, not code.
   Reader: me and the plan reviewer.
   Material: answers to the opening questions: ‹jawaban›. Module layout: ‹struktur›. Team rules: ‹aturan›.
   Limits: feature behind a flag that is off by default; migrations only add; no new library without a written reason.
   Shape: a testable goal, out of scope, file list, tests that must exist, verification commands.
   Check: mark every line that comes from your assumption, not the material.

   Copy prompt

   Learn it in: Prompts for plans and specifications

3. Split a plan into tasks

   Use it when: The plan is approved and you need to split it into small tasks that can each be done in one go.

   Works with any AI assistant.

   Fill in your parts

   FeatureFor example: task deadline reminders by email

   PlanFor example: the reviewed feature plan

   Your prompt

   Goal: I want to split the ‹fitur› plan into small tasks.
   Reader: implementers, people or agents, who will each do one task in one go.
   Material: ‹rencana›.
   Limits: each task leaves the repository green and can be reviewed in one sitting; do not add scope.
   Shape: numbered tasks with files, tests, verification commands and dependencies on other tasks.
   Check: show which tasks can run in parallel without touching the same files.

   Copy prompt

   Learn it in: Prompts for plans and specifications

4. Shared constraints block

   Use it when: Several agents or reviewers will work on one feature and you need shared rules that can be checked.

   Works with any AI assistant.

   Fill in your parts

   FeatureFor example: task deadline reminders by email

   Team rulesFor example: no add-all, no push, no merge

   WorkplaceFor example: one worktree per task

   Your prompt

   Goal: I need a constraints block to copy in full to every implementer and reviewer of ‹fitur›.
   Reader: coding agents and reviewers, who do not remember earlier conversations.
   Material: team rules: ‹aturan›. Workplace: ‹tempat›.
   Limits: short, checkable orders; no vague advice.
   Shape: a numbered list: workplace, prohibitions, commit rules, test rules, when to stop and ask.
   Check: for each rule, write how a reviewer checks it.

   Copy prompt

   Learn it in: Prompts for plans and specifications

5. Implementer brief

   Use it when: One task is going to a coding agent starting from scratch and you need a complete brief.

   Works with any AI assistant.

   Fill in your parts

   Task nameFor example: task 2: due-task selector

   Plan sectionFor example: files, tests and verification for task 2

   Constraints blockFor example: this feature's shared constraints block

   Your prompt

   Goal: I need a brief for one agent doing task ‹tugas›.
   Reader: a coding agent starting from zero.
   Material: the plan section for this task: ‹bagian›. Shared constraints block: ‹batasan›.
   Limits: only files on the list; tests written first and seen failing; stop and ask if the plan is not enough.
   Shape: task, files, tests, verification commands, hand-back report contents.
   Check: the hand-back must include the failing test output, the passing test output and the short repository status.

   Copy prompt

   Learn it in: Prompts for plans and specifications