Skip to content

[Extension]: Update sf to Evernorth OSS repository #5135

Open

Description

@ysumanth06

Extension ID

sf

Extension Name

SFSpeckit — Salesforce Spec-Driven Development

Version

2.0.1

Description

Enterprise-Grade Spec-Driven Development (SDD) Framework for Salesforce.

Author

Sumanth Yanamala / Evernorth

Repository URL

https://github.com/Evernorth/spec-kit-sf

Download URL

https://github.com/Evernorth/spec-kit-sf/archive/refs/tags/v2.0.1.zip

License

Apache-2.0

Homepage (optional)

https://github.com/Evernorth/spec-kit-sf

Documentation URL (optional)

https://github.com/Evernorth/spec-kit-sf#readme

Changelog URL (optional)

https://github.com/Evernorth/spec-kit-sf/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.4.0

Required Tools (optional)

  • sf (>=2.0.0) - required
  • gh (>=2.0.0) - optional

Number of Commands

19

Number of Hooks (optional)

2

Tags

salesforce, enterprise, sdlc, apex, devops

Key Features

  • Enterprise Spec-Driven Development (SDD) for Salesforce with 19 commands
  • 555-point Quality Scoring Rubric across Apex, Flow, LWC, and Metadata
  • Integration with modern Salesforce Code Analyzer v5
  • Blast radius analysis and architecture guardrails
  • Automated test generation and verification evidence generation
  • Bundled SDD templates and Story 00 scaffolding pattern

Testing Checklist

  • Extension installs successfully via download URL
  • All commands execute without errors
  • Documentation is complete and accurate
  • No security vulnerabilities identified
  • Tested on at least one real project

Submission Requirements

  • Valid extension.yml manifest included
  • README.md with installation and usage instructions
  • LICENSE file included
  • GitHub release created with version tag
  • All command files exist and are properly formatted
  • Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

  • Transferred repository to official Evernorth Open Source Software organization (Evernorth/spec-kit-sf).
  • Upgraded repository license to Apache License 2.0 with corporate dual-attribution NOTICE.
  • Released version v2.0.1 (above legacy v2.0.0) to ensure clean client upgrades via specify extension update.
  • Tested download archive at https://github.com/Evernorth/spec-kit-sf/archive/refs/tags/v2.0.1.zip (HTTP 200, SHA-256: f066096cd556c94f3666167b4e2ae8d49b9bdb6f1577bfa78dfeed2d815e8256).
  • Modernized CLI dependencies to Salesforce Code Analyzer v5 and Salesforce CLI v2.
  • Standardized on Story 00 scaffolding pattern across all lifecycle commands and templates.

Example Usage

specify extension add sf --from https://github.com/Evernorth/spec-kit-sf/archive/refs/tags/v2.0.1.zip
/speckit.sf.setup
/speckit.sf.constitution

Proposed Catalog Entry

{
  "id": "sf",
  "name": "SFSpeckit — Salesforce Spec-Driven Development",
  "description": "Enterprise-Grade Spec-Driven Development (SDD) Framework for Salesforce.",
  "author": "Sumanth Yanamala / Evernorth",
  "version": "2.0.1",
  "download_url": "https://github.com/Evernorth/spec-kit-sf/archive/refs/tags/v2.0.1.zip",
  "repository": "https://github.com/Evernorth/spec-kit-sf",
  "homepage": "https://github.com/Evernorth/spec-kit-sf",
  "documentation": "https://github.com/Evernorth/spec-kit-sf#readme",
  "changelog": "https://github.com/Evernorth/spec-kit-sf/blob/main/CHANGELOG.md",
  "license": "Apache-2.0",
  "category": "process",
  "effect": "read-write",
  "requires": {
    "speckit_version": ">=0.4.0",
    "tools": [
      {
        "name": "sf",
        "version": ">=2.0.0",
        "required": true
      },
      {
        "name": "gh",
        "version": ">=2.0.0",
        "required": false
      }
    ]
  },
  "provides": {
    "commands": 19,
    "hooks": 2
  },
  "tags": [
    "salesforce",
    "enterprise",
    "sdlc",
    "apex",
    "devops"
  ]
}

Additional Context

This is an update to an existing catalog entry.
sf was previously registered in catalog.community.json under personal repository ysumanth06/spec-kit-sf (PR #2208). SFSpeckit has now officially migrated into the Evernorth open source organization (Evernorth/spec-kit-sf).
This update refreshes the repository URLs, documentation URLs, download archive URL, version (bumped to 2.0.1 above legacy 2.0.0), and license (Apache-2.0).

Activity

  1. added
    triage-must-haveVerdict: high-value, important work for Spec Kit — do first
    on Oct 27, 2026
  2. github-actions commented on Oct 27, 2026

    @github-actions
    Contributor

    cc @github/spec-kit-maintainers — new catalog submission for review.

  3. added a commit that references this issue on Oct 27, 2026
    ccda220
  4. github-actions commented on Oct 27, 2026

    @github-actions
    Contributor

    Pull request created: #5138

    Generated by Add Community Extension from Issue Submission · copilot · gpt53codex · 32.5 AIC · ⌖ 0.723 AIC · ⊞ 25.4K

  5. KSchlobohm commented on Oct 27, 2026

    @KSchlobohm
    Contributor

    The Copilot code reviewer found that the change must increase the extension version before we can merge so existing users can receive the updated extension through normal updates. Please publish a newer release and align the manifest, catalog version, and download URL. Maintainers will review the updated revision.

  6. ysumanth06 commented on Oct 27, 2026

    @ysumanth06
    ContributorAuthor

    @KSchlobohm Thank you for the guidance! We have published release v2.0.1 under Evernorth OSS (Evernorth/spec-kit-sf), which is strictly above the legacy repository's v2.0.0 release to ensure seamless updates for existing users.

    The manifest, catalog entry, documentation, and download URL have all been updated and aligned:

    • Release Tag: v2.0.1
    • Download URL: https://github.com/Evernorth/spec-kit-sf/archive/refs/tags/v2.0.1.zip
    • SHA-256: f066096cd556c94f3666167b4e2ae8d49b9bdb6f1577bfa78dfeed2d815e8256
    • Number of Commands: 19 (includes new speckit.sf.analyze command and 9 bundled SDD templates)
    • License: Apache-2.0

    I have also updated the issue description above to reflect v2.0.1. Ready for maintainer review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions