Issue Workflow:

Find out if there is an existing Issue already

Description

Expected behavior

Reference to the knowledge base

Design User Stories

Design System Components

Architecture and Data Flows in Tech

Start the required conversations

Solution

Recap

Files Changed

Development Workflow:

Create an Issue in Seed

Our Clerk creates the Issue in GitHub and adds the link to

The Issue is shared with your Coding Agent

Worktree in your computer

Grill Me

Find Edge Cases.

Deepen the context understanding the current Model.

Implementation Plan

Create the Pull Request on Github

Developer reviews the code structure from the Pull Request

User Story Workflow:

Define the name.

User actions.

Component information.

Acceptance criteria.

Security Auditor

Tasks for agents and engineers Output: Secure and Robust Software. Comments

Knowledge Augmented Process

We are offering our services to other knowledge communities in knowledge management. To offer this service successfully, we must excel at managing knowledge. Keep this in mind: Let's be confident because we have the right primitives and foundations. Engelbart's Augmentation Conceptual Framework is still intact. What do we need to do? List of next improvements:

Issues (and Bugs) new workflow

The current workflow that I am trying with Start by creating an issue in Github. Assign it to a developer who will be responsible for reviewing and merging the code. Mention @ion-lion so the agent will know that this is their responsibility. Ion should reproduce the bug, post the repro, fix the code, send a PR with the same repro demonstrating the fix. Then the developer who is assigned will review and merge the code. In many cases they don't need to test at all, because the testing should be done by Ion.