forge-quick-spec

FORGE Quick Track — Spec + direct implementation for bug fixes and small changes (< 1 day of work). Use when the user says "fix this bug", "quick fix", "small change", "patch this", "just fix the login issue", "minor tweak", "hotfix", or has a small, well-defined change that doesn't need full planning/architecture phases. Skips PRD and architecture — goes straight to spec and implementation. Do NOT use for multi-story features or large changes (use /forge-build with proper planning). Do NOT use for test-only tasks (use /forge-quick-test or /forge-verify). Usage: /forge-quick-spec "change description"

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "forge-quick-spec" with this command: npx skills add fwehrling/forge/fwehrling-forge-forge-quick-spec

/forge-quick-spec — FORGE Quick Track

Fast-track mode for bug fixes and small changes (<1 day). Skips the planning and architecture phases.

Workflow

  1. Load context (if FORGE project):

    • Read .forge/memory/MEMORY.md for project context (if exists)
    • forge-memory search "<change description>" --limit 3 (if available)
  2. Classify the request: Bug fix or small feature change?

Bug Fix Track

  1. Root cause analysis (in-memory, no artifact):

    • Reproduce: Steps to reproduce, expected vs. actual behavior
    • Identify cause: Pinpoint the root cause (not just the symptom)
    • Affected components: Frontend / Backend / Database / External services
    • Code location: File path, function/method, line range
  2. Impact & risk assessment:

    • Severity: Blocker / Major / Minor / Trivial
    • Affected users: Scope of impact
    • Side effects: What else could this fix break?
    • Rollback plan: How to revert if the fix causes regression
  3. Write regression tests first (TDD):

    • Test that reproduces the bug (must fail before fix)
    • Unit tests for the fix
    • Functional test covering the user flow
  4. Implement the fix

  5. Validate:

    • Regression test now passes
    • All pre-existing tests still pass (non-regression)
    • Lint + typecheck clean
    • Side effects verified
  6. Propose the commit (format: fix: <description>)

Small Change Track

  1. Analyze the request
  2. Generate a quick spec (in-memory, no artifact)
  3. Write tests (unit + functional for the change)
  4. Implement the change
  5. Validate (lint + typecheck + tests)
  6. Propose the commit

Save Memory

  1. Save memory (ensures fix context persists for avoiding repeated issues):

    forge-memory log "Quick-spec terminé : {DESCRIPTION}, {N} tests" --agent dev
    forge-memory consolidate --verbose
    forge-memory sync
    
  2. Report to user:

    FORGE Quick Track — Complete
    ──────────────────────────────
    Type      : Bug Fix | Small Change
    Change    : <description>
    Tests     : X unit + Y functional (all passing)
    Lint/Type : clean
    
    Commit proposed:
      fix: <description>
    

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

forge-team

No summary provided by upstream source.

Repository SourceNeeds Review
General

forge-build

No summary provided by upstream source.

Repository SourceNeeds Review
General

forge-plan

No summary provided by upstream source.

Repository SourceNeeds Review