feat(workshops/quality-engineering): add platform story coverage + delivery variants#123
Conversation
…livery variants - Update README.md (cloud-agent baseline) with Platform Context section, cross-surface callout blocks, and variant links - Create README.platform.md for Desktop + Cloud delivery workflow - Create README.local.md for CLI / Devin Local terminal-native workflow All variants share the same lab structure (3 tracks, 9 labs) with workflow steps adapted for each delivery surface.
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Addresses Devin Review feedback: all paste-into-Devin prompts now use triple-backtick fenced code blocks per AGENTS.md rules. Also removes redundant Desktop integration callout (content already in Tip block).
There was a problem hiding this comment.
🚩 DeepWiki references omitted from Desktop and CLI variants
The Cloud variant (README.md) includes "Step 3 (Optional): Read the DeepWiki" in each lab, but both new variants (README.local.md and README.platform.md) omit this step entirely. The REVIEW.md rule says "Knowledge notes, DeepWiki, MCP integrations, and playbooks should be referenced where relevant." The omission is likely deliberate: the local/desktop variants replace the DeepWiki step with a hands-on monitoring/iteration step that better fits the local workflow. However, a brief mention (e.g., "See also the repo's DeepWiki for architecture context") would satisfy the shared-context-layer rule without disrupting the flow.
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Acknowledged — this is intentional. The local/desktop variants replace the "Read the DeepWiki" step with hands-on exploration steps (running devin locally, using Cascade for code exploration) which serve the same purpose of understanding repo architecture but through direct interaction. The Cloud variant keeps DeepWiki as a separate step because it's browser-based. Will leave as-is since the local workflow achieves the same goal through a different path.
…locks Converts 6 standalone operational prompts from italic format to fenced code blocks: coverage analysis, subagent delegation, mutation iteration, app setup, and performance analysis prompts.
| ``` | ||
| Analyze the current test coverage. Run the existing tests and generate a | ||
| coverage report. What are the top 5 modules with the lowest test coverage? | ||
| What testing patterns does the codebase use? | ||
| ``` |
There was a problem hiding this comment.
🚩 CLI variant prompts intentionally omit repo names due to local context
The AGENTS.md rule states "Prompts must include repo names, file paths, and expected output format." In README.local.md, most prompts omit the repo name (e.g., line 91-95 says "Analyze the current test coverage" without naming the repo). This is because the CLI workflow has the user cd into the repo and run devin first (e.g., lines 84-87), so Devin already has project context. The cloud variant (README.md) and platform variant (README.platform.md) correctly include repo names since their prompts are sent to cloud agents without local context. This is a deliberate adaptation, not an oversight — but it's worth noting that the AGENTS.md rule doesn't explicitly carve out an exception for CLI-context prompts.
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Correct — this is deliberate. In the CLI workflow, users cd into the repo and run devin, so the agent already has full project context. Including the repo name in the prompt would be redundant since Devin CLI inherits the working directory. The cloud/platform variants include repo names because those prompts go to agents without local filesystem context.
Rename 'Subagent A/B' to 'Session A/B' since these are independent CLI sessions in separate terminals, not subagents within a single session. Aligns with Repos Required section which already used 'Session B'.
| - **Leverage shell integration.** Devin CLI understands your shell context, recent commands, and terminal state — no need to re-explain your environment. | ||
| - **Iterate fast locally.** The local workflow lets you review changes instantly (`git diff`), test them immediately (`npm test`), and refine your instructions in real time. | ||
| - **Build up knowledge as you go.** Save testing conventions (framework choices, assertion style, test data patterns) as Knowledge items — they apply to CLI sessions too. | ||
| - **Hand off to Cloud when needed.** Some labs (scheduled sessions, long-running tests) benefit from Cloud execution. Use `devin --cloud` or hand off mid-session when the task outgrows local resources. |
There was a problem hiding this comment.
The devin --cloud flag referenced on line 42 of workshops/quality-engineering/README.local.md does not exist in the Devin CLI. The correct mechanism for cloud handoff is the /handoff slash command inside an interactive CLI session.
Line 42 currently reads:
Use `devin --cloud` or hand off mid-session when the task outgrows local resources.
Should be updated to something like:
Use the `/handoff` command inside a CLI session to send the task to Cloud when it outgrows local resources.
This was identified as the same mistake found and fixed in PR #128 (security demos).
Summary
Adds platform delivery variants to the quality-engineering workshop, following the conventions in
shared/WORKSHOP-VARIANTS.md.Changes to
README.md(cloud-agent baseline):README.platform.md,README.local.md)New
README.platform.md(Desktop + Cloud variant):New
README.local.md(CLI / Devin Local variant):devinCLIAll three variants share identical lab structure (3 tracks, 9 labs, same repos and modules).
Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/e4434f1d4a914181af8af57aea07d2f9
Requested by: @bsmitches