feat: auto-seed onboarding automation with two-phase workflow#16
Merged
arjunastha merged 1 commit intosafe-agentic-framework:mainfrom Feb 21, 2026
Merged
Conversation
bishnubista
force-pushed
the
feat/auto-seed-onboarding
branch
from
b4fad17 to
46b0b21
Compare
Replace the single use-case-claim template with two focused forms: - "Propose New Use Case" for new seeds (with industry dropdown + NAICS mapping) - "Claim Existing Seed" for picking up existing seeds to write up Add a two-phase GitHub Action (auto-seed.yml): - Phase 1 (issue opened): assigns next SAFE-UC ID, renames issue, assigns author - Phase 2 (maintainer comments /accept): runs scaffold, creates branch + PR Add reusable scaffold script (scaffold-use-case.sh) that creates the seed folder, README, registry entry, and README index row — with rollback on failure and validation integration. Update README with "Don't see your use case?" callout linking directly to the proposal form. Signed-off-by: bishnubista <bista.developer@gmail.com> Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
bishnubista
force-pushed
the
feat/auto-seed-onboarding
branch
from
46b0b21 to
27ca67a
Compare
techstar9797
pushed a commit
to techstar9797/safe-agentic-use-cases
that referenced
this pull request
Mar 17, 2026
…to-seed-onboarding feat: auto-seed onboarding automation with two-phase workflow
techstar9797
pushed a commit
to techstar9797/safe-agentic-use-cases
that referenced
this pull request
Mar 17, 2026
…to-seed-onboarding feat: auto-seed onboarding automation with two-phase workflow Signed-off-by: Sachin Keswani <sachin.news@gmail.com>
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
use-case-claim.ymltemplate with two focused issue forms: Propose New Use Case (5 fields with industry dropdown + NAICS mapping) and Claim Existing Seed (3 fields for picking up existing seeds)auto-seed.yml): Phase 1 assigns the nextSAFE-UCID on issue open; Phase 2 scaffolds the seed and creates a PR only when a maintainer comments/acceptscaffold-use-case.sh) that creates the seed folder, README, registry entry, and README index row — with rollback on failureuse-case,proposal,claim,triage,seededHow it works
SAFE-UC-XXXXID, renames issue, assigns author/accept→ scaffold runs, branch + PR createdFiles changed
.github/ISSUE_TEMPLATE/propose-new-use-case.yml.github/ISSUE_TEMPLATE/claim-existing-seed.yml.github/ISSUE_TEMPLATE/use-case-claim.yml.github/workflows/auto-seed.yml/acceptscripts/scaffold-use-case.shREADME.mdTest plan
validate_contributions.shpasses after scaffold and after cleanupuse-case,proposal,claim,triage,seeded)🤖 Generated with Claude Code