Skip to content

matteocodogno/wellforge

v2.61.0MIT

Full-stack AI-assisted development: spec-driven workflow, role-based agent team, orchestrator, scaffolder, lifecycle upgrades, quality-gate and eval enforcement.

spec-driven

WellForge spec-driven development conventions: the spec → plan → tasks workflow, file formats, status lifecycle, and drift rule. Use whenever working in a project that has a specs/ directory, when the user mentions a spec, feature specification, or task list, when implementing any task that references a specs/NNN-slug/ path, or when asked about the status of a feature. Also the authoritative reference for the $wf-spec, $wf-plan, $wf-design, and $wf-tasks commands — they MUST follow this format exactly.

Read SKILL.md at the source

Pinned to revision 8d5a09502718, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.