Update input requirements for /speckit.plan

Removed reference to 'instructions.md' as input for /speckit.plan invocation.

Author: JackTreble

.github/workflows/product-architect.md

@@ -56,7 +56,7 @@ Portfolio focus reminder: prioritize tools that replace paywalled or heavily res
   - Create a feature directory in `specs/[feature-slug]/`
   - Generate `spec.md` following `.specify/templates/spec-template.md`
 4. **Generate planning artifacts with `/speckit.plan` and `/speckit.tasks`**
-  - Invoke `/speckit.plan` using the `The Tech` section of the triggering issues content and the contents of `instructions.md` as input.
+  - Invoke `/speckit.plan` using the `The Tech` section of the triggering issues content as input.
   - Ensure the plan stays grounded in the approved issue scope.
   - Invoke `/speckit.tasks` from the generated plan output.
   - Produce/update planning files under `specs/[feature-slug]/`
@@ -107,4 +107,4 @@ You **must** always call at least one safe-output tool before finishing.
 - **Spec or data missing**: if the issue body lacks sufficient detail to generate a plan, call `add_comment` on the triggering issue to request a proper spec via `/speckit.specify`, then stop.
 - **Any other failure**: call `add_comment` on the triggering issue with a brief summary of what went wrong.
 
-Never finish this workflow without calling at least one safe-output tool. Producing zero outputs is always incorrect.
+Never finish this workflow without calling at least one safe-output tool. Producing zero outputs is always incorrect.