feat(workshops/application-development-maintenance): add platform story coverage + delivery variants#125
Conversation
…ry coverage + delivery variants - Update README.md (cloud variant) with Platform Context section, variant links, Desktop/CLI callout blocks, and Agent Command Center tip - Add README.platform.md for Desktop + Cloud delivery: reframe workflow around Spaces, Cascade/Devin Local, Cloud delegation, Agent Command Center, and one-click PR checkout - Add README.local.md for CLI / Devin Local delivery: terminal-native workflow with subagents, shell integration, and Cloud handoff notes
🤖 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:
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
There was a problem hiding this comment.
📝 Info: README.md fixes pre-existing 'Open a PR' rule violation in Lab B2 prompt
The old Lab B2 Option A prompt ended with ...and open a PR with your fix and root cause analysis. which violated the REVIEW.md rule: 'No "Open a PR" — Devin opens PRs by default.' The fix at line 343 correctly changes this to ...and include a root cause analysis. The new variant files (README.local.md:370 and README.platform.md:360) use appropriately different phrasing that also avoids this violation.
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Fixed in 35c37c0 — removed open a PR from the Lab B2 Option A prompt in README.md for consistency with the variant files and AGENTS.md rules.
| - *"How should a team handle dependency upgrades that break the build — auto-revert and flag, or block and notify?"* | ||
| - Consider creating a **Devin Knowledge item** capturing the dependency upgrade policy | ||
|
|
||
| > **Desktop tip:** When running dependency upgrades across multiple repos, use the Agent Command Center in Devin Desktop to track all sessions on a single Kanban board — see which repos have completed, which are in progress, and which need review. | ||
|
|
||
| #### Step 3 (Optional): Set Up a Scheduled Session | ||
|
|
||
| Once you're happy with the output from step 1, turn it into a recurring task: |
There was a problem hiding this comment.
📝 Info: README.md fixes pre-existing garbled prompt text in Lab C1
The diff reveals that the old README.md had garbled prompt text in three places in Lab C1:
- Step 1:
...document it.md\listing...→ now correctly reads...document why. Create a `DEPENDENCY_UPDATES.md` listing...` (line 468) - Step 3:
...note it.md.→...note it in a DEPENDENCY_UPDATES.md.(line 486) - Step 4:
...works.md\.→...works. Document the changes in a `DEPENDENCY_UPDATES.md`.` (line 494)
These were clearly copy-paste or editing artifacts where markdown backtick formatting collided with sentence text. The fixes are correct and the new files (README.local.md, README.platform.md) use the corrected versions throughout.
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Fixed in 35c37c0 — applied the same garbled prompt text fixes to README.md Lab C1 (lines 468, 486, 494) for consistency across all three variants.
… Lab B2 - Fix corrupted 'it.md' / 'works.md' references in Lab C1 prompts across all three variants to properly reference DEPENDENCY_UPDATES.md - Remove 'open a PR' from Lab B2 Option A prompt in README.md (Devin opens PRs by default per AGENTS.md rules)
| - **Delivery surface:** Devin CLI / Devin Local — participants work directly in their terminal with local file access, shell integration, and subagents for parallel work | ||
| - **Devin value themes woven throughout:** |
There was a problem hiding this comment.
🚩 New files use 'Delivery surface' and 'Devin value themes' terminology in Context sections
README.local.md:721 uses **Delivery surface:** Devin CLI / Devin Local and README.platform.md:701 uses **Delivery surface:** Devin Desktop + Devin Cloud. The term 'Delivery surface' is somewhat internal/sales terminology. Similarly, 'Devin value themes woven throughout' (README.local.md:722, README.platform.md:702) reads as enablement language. However, the base README.md already uses 'Devin value themes woven throughout' at line 682 (pre-existing), and the content following these terms is genuinely useful for attendees understanding their workshop platform. The REVIEW.md rule targets 'presales positioning' specifically, and this content is more descriptive than positioning. Borderline but likely acceptable.
Was this helpful? React with 👍 or 👎 to provide feedback.
1 participant
Summary
Adds Cognition Platform story coverage to the Application Development & Maintenance workshop with three delivery variants per the
WORKSHOP-VARIANTS.mdconvention.Changes to
README.md(cloud-agent baseline):## Platform Contextsection after Overview explaining this is the Devin Cloud / web-app workflowREADME.platform.md,README.local.md)> **Desktop tip:**,> **CLI alternative:**) throughout existing labs where natural — Labs A1, A2, B1, C1, C3it.md/works.md→ properDEPENDENCY_UPDATES.mdreferences)open a PRin Lab B2 prompt (violates AGENTS.md rule — Devin opens PRs by default)New
README.platform.md(Desktop + Cloud variant):New
README.local.md(CLI / Devin Local variant):devinCLIdevin→ provide prompt interactively → iterate in conversation → use subagents → hand off to Cloud if needed> **Cloud handoff:**callouts for labs requiring cloud-only features (scheduled sessions, browser-based bug hunting)> **Desktop integration:**note about ACP compatibilityAll three variants share the same lab structure (tracks A/B/C, labs 1-3 each) for cross-referencing.
Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/3e4e7c0454f1470a81d818a04c6ef0ed
Requested by: @bsmitches