feat(skills): add pending integration stub pattern across delivery lifecycle - #82
Open
lauraCoxItential wants to merge 3 commits into
Open
Conversation
Derived from useCase-lightningAi — captures the pattern for building and demonstrating delivery progress when customer integrations aren't yet finalized. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
When a customer's integrations aren't yet finalized, delivery no longer
has to stop. Introduces a consistent stub pattern across all three agents:
- solution-arch-agent: new ⚠ Stub feasibility status (distinct from
Blocked); Design stage produces integration-model-{name}.json stubs
and integration-questions.md customer questionnaire per pending adapter
- builder-agent: new Pending Integration Pattern section — stub workflow
per integration (one core connectivity action), newVariable placeholder
task pattern with pending_adapter sentinel, as-built Activate section
with pre-filled replacement task JSON
- qa-agent: pending-adapter test case type, ⏳ Pending adapter report
status — criteria blocked by a pending adapter are accepted residuals,
not failures
- AGENTS.md: four new rules from Lightning AI engagement (rules 26-29) —
cloud OAuth-only auth, flat .data.variables path, template group field,
service account Admin Essentials navigation
Derived from useCase-lightningAi — EmailOpensource stub + 10 integration
model files.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When a customer's integrations are known but not yet finalized, delivery no longer has to stop. This PR introduces a consistent stub pattern across all three delivery agents so engineers can build, test, and demonstrate progress now — and activate the real adapters with a single targeted update later.
Changes
⚠ Stubfeasibility status (distinct from⚠ Blocked); Design stage producesintegration-model-{name}.jsonOpenAPI stubs andintegration-questions.mdcustomer questionnaire for each pending integrationnewVariableplaceholder task withpending_adaptersentinel, as-built Activate section with pre-filled replacement task JSONpending-adaptertest case type and⏳ Pending adapterreport status — criteria blocked by a pending adapter are accepted residuals, not failures.data.variablespath, templategroupfield cannot be empty, service account Admin Essentials navigationdocs/superpowers/specs/2026-07-09-pending-integration-stub-pattern-design.mdSource
Derived from
useCase-lightningAi— EmailOpensource adapter not installed on customer cloud instance, 10 integration model files produced during design phase.Testing
feature/convention per CONTRIBUTING.md⚠ Stubvs⚠ Blockeddistinction is clearpending-adaptertype is consistent with existing case types🤖 Generated with Claude Code