Update framework skills,docs and linting pre-commit#5
Merged
Conversation
Complete final editorial pass of the framework philosophy document, tighten wording for consistency, and add explicit opinionated contracts for feature directory lifecycle management and branch/worktree naming alignment (including slashless branch names).\n\nCo-Authored-By: Oz <oz-agent@warp.dev>
Integrate a first-class Feature concept into the framework while keeping Deliverable as the bounded unit of agent-completed work. Clarify that docs root is flexible but framework shape is opinionated with required standards/ and features/ directories, and add explicit living SPEC maintenance guidance across enhancements, bug fixes, and rework.\n\nCo-Authored-By: Oz <oz-agent@warp.dev>
Refine framework philosophy to explicitly distinguish long-lived Feature SPECs from per-deliverable Deliverable SPECs, clarify cross-cutting Feature and Milestone semantics, and tighten opinionated documentation naming/structure guidance while preserving flexible docs root support. Also update convergence loop and key principles to reflect deliverable-level iteration plus feature-level specification evolution.\n\nCo-Authored-By: Oz <oz-agent@warp.dev>
Update the framework to treat Features as long-lived user-journey/requirements objects via a Feature Requirements Document (FRD), while reserving SPEC terminology for deliverables. Clarify many-to-many feature↔deliverable requirement mapping, milestone-gated feature capability maturation, and consistent document naming/flow guidance.\n\nCo-Authored-By: Oz <oz-agent@warp.dev>
Refine framework documentation architecture to separate features and deliverables into distinct directories, formalize deliverable-to-feature linkage rules (including shared support work and feature-agnostic chores), and clarify proposal semantics as optional ideation artifacts that can attach to features, deliverables, or both.\n\nCo-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
- add phase-1 Codex policy doc and role configs\n- enable repo-level .codex multi-agent settings for worker/qa/monitor\n- switch framework references to canonical zazz-skills GitHub doc and remove local duplicate\n\nCo-Authored-By: Oz <oz-agent@warp.dev>
- analyze upstream-as-is vs forked local adoption paths\n- add sqlite, lock-authority, and mcp-vs-cli token-efficiency assessment\n- define required switchman coordination policy for multi-agent mode\n\nCo-Authored-By: Oz <oz-agent@warp.dev>
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
2 participants
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.
Summary
This PR updates the board repo to match the latest canonical framework skills and improves the repo’s local reference-implementation setup.
It includes:
zazz-skills.agents/skill-extensions/scaffoldingzazzctlwrapper cleanup so the repo-level script points to the canonical board API CLI.zazz/features/Verification
npm run lintcd api && set -a && source .env && set +a && NODE_ENV=test npm run testNotes
husky+lint-staged