[Amber Refactor] Update the Start spec-kit workflow's welcome greeting and subsequent command suggestions with proper nomenclature

[kami619]

Current State

Steps to Reproduce:

1. User logs into an existing workspace in the Ambient Code platform.
2. Creates a session with a specific model.
3. Selects the Start spec-kit the spec driven development workflow.
4. User observes the following in the chat window.

When we create the SDD workflow in ACP., it gives us the one of the two options of the below mentioned greeting text.,

Option 1:

Hello! 👋

The spec-kit workflow is now active. This workflow helps you with:

Feature Development & Documentation:

Creating and refining feature specifications
Generating implementation plans with design artifacts
Breaking down features into actionable, dependency-ordered tasks
Running consistency checks across your spec, plan, and task artifacts
Customizing checklists and clarifying underspecified requirements
Project Governance:

Establishing and maintaining your project constitution (core principles and standards)
Keeping all templates synchronized with your project values
I have access to specialized sub-agents across engineering, product, UX, and documentation disciplines who can provide expert perspectives when needed. Feel free to ask me to help with any phase of your feature development process!

What would you like to work on?

Option 2:

Hello! The SpecKit workflow is now active.

This workflow helps you transform feature ideas into well-structured, implementation-ready specifications. It guides you through:

Specifying features from natural language descriptions
Clarifying requirements through targeted questions
Planning implementation with design artifacts
Generating actionable, dependency-ordered tasks
Analyzing consistency across your specs, plans, and tasks
You can invoke these capabilities using commands like /specify, /clarify, /plan, /tasks, /analyze, and others.

What feature would you like to work on?

In both cases, User of the ACP SDD worfklow is not guided with the right command palette., with the prefix /speckit. below is just an example and not an exhaustive list of all the commands.

/speckit.clarify - If you want to identify any underspecified areas (though validation shows spec is complete)
/speckit.plan - Generate implementation plan with design artifacts
/speckit.analyze - Run cross-artifact consistency analysis (after creating plan and tasks)

Desired State

We would want the welcome greeting text in the Start spec-kit workflow to indicate the right command palette with the /speckit. prefix instead of /specify or /clarify command suggestions as they won't work without the prefix in place.

Constraints & Requirements

make sure the changes are well tested and unit tests and integration tests exists for them before the implementation of the re-factor.

Priority

P1 - High (Tech debt)

Confirmation

• I have reviewed CLAUDE.md standards
• Backward compatibility is required
• I will review the generated PR before merging

[github-actions]

Amber Change Summary

The following files were modified:

 .../components/welcome-experience.tsx              |   2 +-
 components/runners/claude-code-runner/main.py      | 707 +++++++++++++--------
 2 files changed, 444 insertions(+), 265 deletions(-)

Next Steps:

• Review that changes match the issue description
• Verify no scope creep or unintended modifications
• A PR will be created shortly for formal review

---

🔍 View AI decision process (logs available for 90 days)

[github-actions]

🤖 Amber has created a pull request to address this issue: #524

The changes are ready for review. All automated checks will run on the PR.

---

🔍 View AI decision process (logs available for 90 days)