Fcs Writing Plans

Writing plans

Plan must include

• A short goal.
• 3-7 concrete steps (file edits, new files, config changes).
• Tests or verification.
• Risks and fallback.

Process flow

digraph fcs_writing_plans {
  "Receive approved design" [shape=box];
  "Scope check" [shape=box];
  "Map file structure" [shape=box];
  "Draft plan (tasks + steps)" [shape=box];
  "Save to docs/plan/" [shape=box];
  "Summarize + ask to execute" [shape=doublecircle];

  "Receive approved design" -> "Scope check";
  "Scope check" -> "Map file structure";
  "Map file structure" -> "Draft plan (tasks + steps)";
  "Draft plan (tasks + steps)" -> "Save to docs/plan/";
  "Save to docs/plan/" -> "Summarize + ask to execute";
}

Output

• Always write the plan into a markdown file under docs/plan/.
• File name format: {dd-mm-yyyy}-{kebab-case-name}-plan.md (example: 10-03-2026-api-cache-plan.md).
• If docs/plan/ does not exist, create it.
• The response should reference the created file and briefly summarize its contents.
• Hard stop after writing the plan: ask whether to continue in the current context or switch to a new context and use the created plan. Do not start implementation.
• Also ask whether to create an analysis markdown in docs/analysis/ instead of moving to executing plans.

Rules

• Avoid overly detailed micro-steps.
• If information is missing, ask 1-2 clarifying questions.
• Mention target files and direction of changes.

Language

• Respond in Czech per the communication-standard skill.