Automated Workflows

Workflows empower you to automate complex, multi-stage engineering tasks by defining structured instructions for Sypha. You can trigger any workflow instantly by typing /[workflow-filename.md] in the chat interface.

Coming Soon !!!

Initializing Workflows

Workflows are standard Markdown files stored in specialized directories:

• Global Repository: ~/.sypha/workflows/ (Available across all IDE instances).
• Project Repository: [your-project]/.sypha/workflows/ (Shared with your team via version control).

Rapid Setup

1. Authorise a new .md file with a sequential list of instructions.
2. Deposit the file into your chosen workflows directory.
3. Execute the workflow by typing /name-of-file.md to execute.

Workflow Capabilities

Workflows can orchestrate Sypha’s entire toolchain:

• Internal Tools: read_file(), search_files(), execute_command().
• CLI Ecosystem: Direct interaction with git, docker, npm, terraform, etc.
• External Integrations (MCP): Communicating with Slack, JIRA, production databases, and cloud APIs.
• Multi-Tasking: Utilise Tailored Modes to delegate sub-logic to the most efficient engine.

Prototype Workflow Patterns

1. Architectural Code Review

1. Scan for `TODO` or `DEBUG` comments across changed files.
2. Execute the local linting engine (`npm run lint`).
3. Run critical unit tests.
4. Authorise a PR summary based on recent commit history.

2. Environment Initialization

1. Provision a new branching structure for the feature.
2. Initialize temporary development databases.
3. Seed the environment with mock data.
4. Verify service availability before handing control to the developer.

3. Automated Release Lifecycle

1. Synthesize all merged PRs since the last version tag.
2. Generate a structured changelog.
3. Update versioning in `package.json` or manifest files.
4. Notify the engineering Slack channel of the deployment status.

Practical Example: Automated PR Submission

Create submit-logic.md in your .sypha/workflows folder:

# PR Submission Protocol

1. Utilise `search_files` to verify no sensitive keys or debug logs are present.
2. Execute the test suite via `execute_command`.
3. If successful, stage all relevant changes and commit with an atomic message.
4. Push the branch and initialize a PR using the `gh` CLI.
5. Ask for the final PR title and designated reviewers.

By executing /submit-logic.md, Sypha manages the entire 5-step process autonomously, ensuring consistency and preventing manual oversight.

Visit the Sypha Workflow Gallery for community-contributed automation templates.