Add agent working guidance (ticket style, PR style, way of working)#132
Merged
Conversation
Record how work in this repo is planned, tracked, validated, and written up: artifact routing between Linear and the repo, the ticket altitude contract and template (including the ready-for-agent Agent spec), and what a PR description must carry. Ported from the figments repo and adapted to Lash's real paths (docs/adr, runbooks, docs/PUBLISHING.md, the confidence gate and push gate).
Document the Linear mechanics for this repo (project lash on team figments, FIG keys, mcp__linear__* operations, parent/child efforts), the two dispatch labels and the triage roles that map to workflow states instead, and how the engineering skills should consume CONTEXT.md and docs/adr.
docs/ is rsynced verbatim to lash.run, so contributor process guidance placed beside the site sources would ship as public pages. Exclude the directory from the Pages build instead of moving the docs away from the figments layout.
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.
lash had no documented agent-facing process guidance. Ports the non-project-specific parts of figments'
docs/agents/corpus, adapted to lash's real paths and facts.Adds
docs/agents/: way-of-working (artifact routing, definition of done, triage dispatch, runbook + ADR norms), ticket-style (the altitude contract — a ticket says what/why/done-when, not how to build it — plus the template, the+++collapsible convention and the ready-for-agent Agent-spec form), pr-style, issue-tracker, triage-labels, domain.Also excludes
docs/agents/from the published site.docs/is rsynced verbatim into the Pages artifact, so unlinked markdown there is still served at lash.run — this would have published internal Linear/triage process guidance.lint_docs.pyonly walks*.html, so nothing would have flagged it.Adapted to lash: Linear team
figments/ projectlash/FIG-<n>keys;docs/adr/(49 ADRs, with the real grandfathered duplicate numbers noted);runbooks/<scenario>/runbook.mdand lash's two-layer scripted-vs-agent-judged split; definition of done tied tojust push-gateand CONTRIBUTING's dual-geometry E2E requirement; the rootCONTEXT.mdglossary. Stripped as figments-only: Wayfinder entirely, figments product/architecture nouns, their tracing MCP and reset harness,just crate2nix.Rewrote pr-style's "the PR body is not durable history" — in lash the squash body is durable and feeds releases, so the
Release-Notes:requirement is a first-class PR rule.Docs lint passes. (
AGENTS.md/CLAUDE.mdgained a linking "Agent skills" section locally; both are gitignored so they are absent from this commit by design.)