sifter-ai/sifter / .agents/skills/sdd-remote
sdd-remote
VerifiedRemote sync workflow for Story Driven Development. Use this skill whenever the user asks to pull from remote, push changes to SDD Flow, enrich drafts, update local state from remote, publish local updates, process remote drafts, or run a remote worker job (enrich or sync). Also trigger on phrases like "sdd pull", "sdd push", "sync with SDD Flow", "enrich this CR", "push the remote updates", "pull the latest specs".
SDD Remote — Pull, Enrich, Push
Purpose
Synchronize local SDD docs with remote updates (from the SDD Flow server), enrich draft content, and publish the enriched result to remote in active states.
This skill also applies when a remote worker job is dispatched from SDD Flow — the worker runs these same workflows on behalf of the user.
Detection
This workflow applies when:
.sdd/config.yamlexists in the project root with aremote:section configured- The user asks to update local state from remote, pull pending CRs/bugs/docs, enrich drafts, or push pending remote updates
- A remote worker job prompt instructs you to follow this workflow
Before any pull/push operation, check remote configuration with sdd remote status.
Workflows
Enrich workflow — Change Request
Follow this sequence to enrich a draft CR:
- Pull remote drafts:
sdd pull --crs-only
- Generate the draft TODO list:
sdd drafts
-
Enrich the draft with technical details, acceptance criteria, edge cases, and any relevant information from the project documentation and comments.
-
Transition the enriched CR from
drafttopending:
sdd mark-drafts-enriched
- Push the enriched content:
sdd push
Enrich workflow — Document
Follow this sequence to enrich a document (e.g. a feature spec):
- Pull remote drafts:
sdd pull --docs-only
-
Locate the document file in
product/orsystem/and update its content with the enriched version. -
Push the enriched content:
sdd push
If the document was in draft status, it transitions to new on the server.
Sync workflow — Project-level
Full project sync when the user asks for "the latest" or "pull everything and implement":
- Pull the latest specs:
sdd pull
-
Run the
sddskill — it handles the full loop: open bugs, pending CRs, documentation sync, code implementation, mark-synced, and commit. -
Push the local updates:
sdd push
Rules
- Always check remote configuration before pull/push (
sdd remote status). Fail gracefully if not configured. - Do not use
sdd push --allunless the user explicitly asks for a full reseed. - If pull reports conflicts, do not overwrite local files blindly. Report the conflicts and ask how to proceed.
- Do not edit files inside
.sdd/manually. - Keep status transitions explicit: enrich first, then
sdd mark-drafts-enriched, then push. - Always commit before pushing when the sync workflow makes code changes. Push should never carry uncommitted work.
Related commands
sdd remote init— Configure remote for this projectsdd remote status— Show remote config + connectivitysdd pull/sdd pull --crs-only/sdd pull --docs-onlysdd drafts— List draft items to enrichsdd mark-drafts-enriched— Transition enriched drafts to pendingsdd sync/sdd mark-synced— Local sync loop (seesddskill)sdd push— Publish local updates to remote
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |