docs: retain Conductor reference in plan-mode note and update links

docs/cli/plan-mode.md

@@ -412,8 +412,8 @@ To build a custom planning workflow, you can use:
   [custom plan directories](#custom-plan-directory-and-policies) and
   [custom policies](#custom-policies).
 
-> **Note:** Use [Spec-Driven Development (SDD)] as a reference when building
+> **Note:** Use [Conductor] as a reference when building your own custom
-> your own custom planning workflow.
+> planning workflow.
 
 By using Plan Mode as its execution environment, your custom methodology can
 enforce read-only safety during the design phase while benefiting from
@@ -468,4 +468,5 @@ those files are not automatically deleted and must be managed manually.
 [`plan.toml`]:
   https://github.com/google-gemini/gemini-cli/blob/main/packages/core/src/policy/policies/plan.toml
 [Spec-Driven Development (SDD)]: ./spec-driven-development.md
+[Conductor]: https://github.com/gemini-cli-extensions/conductor
 [open an issue]: https://github.com/google-gemini/gemini-cli/issues

docs/cli/spec-driven-development.md

@@ -143,5 +143,4 @@ During implementation, you can also:
 | `/spec revert`    | Reverts a track, phase, or task by analyzing git history.                         | Reverts git history                                                                                                                                              |
 | `/spec review`    | Reviews completed work against guidelines and the plan.                           | Reads `plan.md`, `product-guidelines.md`                                                                                                                         |
 
-[Conductor]:
+[Conductor]: https://github.com/gemini-cli-extensions/conductor
-  https://developers.googleblog.com/conductor-introducing-context-driven-development-for-gemini-cli/