Enhance spec process journal

[dearrudam]

This pull request introduces a comprehensive, unified process for managing feature specs and progress tracking in the SLDD (Specs-Driven, Lean, Disciplined Delivery) workflow. The main change is the formalization of a SPEC.md file as the single source of truth for each feature, with standardized save/resume behaviors, progress checklists, and improved integration of project conventions (such as testing guidelines). Each SLDD skill now supports resuming from and saving to SPEC.md, and the workflow ensures that all steps are tracked and context is preserved throughout the lifecycle.

Key changes include:

Unified SPEC.md process and progress tracking:

• Introduced SPEC.md as a canonical, per-feature process journal, with a standardized directory structure, progress checklist, and sectioned output for each SLDD step. All skills now support saving outputs to and resuming from SPEC.md, ensuring continuity and traceability across the feature lifecycle.

Consistent save/resume behavior across all SLDD skills:

• Each skill now accepts an optional SPEC.md path at initialization, reads completed steps, extracts relevant prior sections as context, and announces which step will be continued. If a specs root directory is provided, the user can select from available features. [1] [2] [3] [4] [5] [6] [7]
• After delivering output, each skill checks for write permissions, asks the user whether to save, and updates SPEC.md accordingly (including marking the checklist). If in plan mode (read-only), the user is informed and saving is deferred. [1] [2] [3] [4] [5] [6]

Integration of project conventions and guidelines:

• Before writing tests or implementation, skills check for an AGENTS.md file and any referenced testing guidelines, ensuring all generated code and tests conform to project standards. This is enforced in both test-writing and implementation steps, and is audited in the verification report. [1] [2] [3]

Enhanced verification and compliance auditing:

• The verification step now explicitly checks test convention compliance (naming, structure, assertions) against the project's guidelines, and includes this as a section in the final gap report.

Improved user experience and workflow clarity:

• All prompts and behaviors for saving, resuming, and directory/slug selection are now consistent and explicit, reducing user error and improving traceability. [1] [2] [3] [4] [5] [6] [7]

These changes standardize the feature development process, ensure all context and decisions are preserved, and tightly integrate project conventions into every step.