The method around your coding agent
From a request to a result you can inspect.
A useful agent needs more than instructions for writing code. It needs to know who the work is for, what completion means, which tools own each step and what the next session must remember. That is the job of the ssheleg harness.
One method, distinct responsibilities
| Layer | What it does | Where it lives |
|---|---|---|
| Routing | Select a capability for the task and state its boundary | Family routers |
| Delivery | Keep scope, dependencies, acceptance evidence and a resume point | task-pipeline |
| Coordination | Claim shared work and record who changed what | agent-sync |
| Specialist skills | Apply product, design, integration and agent engineering contracts | 10 independently usable packs |
| Observation | Inspect enrolled projects, changes and possible credential exposures | Project Observatory |
Your agent remains the runtime. Claude Code, Codex and other hosts execute the model and tools and enforce their permissions. The harness supplies working contracts and checks; it does not create a sandbox.
A task that survives the next session
- Understand. Capture the request and the scenarios it must serve.
- Plan. Name each dependency, owner and completion check.
- Build. Use the specialist pack for the work in front of the agent.
- Verify. Check the artifact that will ship. Keep missing evidence visible.
- Hand over. Save decisions, results and the exact next action in Git.
- Observe. With Observatory installed, inspect project state after the change.
Project Observatory
A local instrument for the projects an agent works on. Enroll explicit folders, inspect Git state and project metrics, and check selected artifacts for known credential values. Findings point to a next action without reproducing the credential.
Separate installation. Explicit access. Installing the skill family does not start Observatory or scan your computer. The portable edition documents its supported scope and the integrations still awaiting migration. Public examples use synthetic projects and credentials.
Borrow mechanisms. Keep one contract.
Our ECC study focuses on installation ownership, bounded hooks, durable handoffs and evaluations tied to the artifact tested. We adapt those ideas to the family's existing contracts. The research records what we adopted, what we already had and what we chose to leave out.