skills-first-workflow
Skill4 starsChanged 10 months agoMITView on GitHub
Use when entering any repository, creating a new repository, or performing repository migration. Automatically enforces prerequisite skill loading and verification before any implementation begins.
- Installs packages
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agents-onboardingSkill
- agent-workitem-automationSkill
- architecture-testingSkill
- aspire-integration-testingSkill
- automated-standards-enforcementSkill
- best-practice-introductionSkill
- branching-strategy-and-conventionsSkill
- broken-windowSkill
- change-risk-rollbackSkill
- ci-cd-conformanceSkill
- component-boundary-ownershipSkill
- contract-consistency-validationSkill
- csharp-best-practicesSkill
- deployment-provenanceSkill
- documentation-as-codeSkill
- documentation-scaffoldSkill
- dotnet-bespoke-code-minimisationSkill
- dotnet-best-practicesSkill
- dotnet-domain-primitivesSkill
- dotnet-efcore-practicesSkill
- dotnet-healthchecksSkill
- dotnet-logging-serilogSkill
- dotnet-mapping-standardSkill
- dotnet-open-source-first-governanceSkill
- dotnet-source-generation-firstSkill
- dotnet-specification-patternSkill
- dotnet-testing-assertionsSkill
- environment-traceabilitySkill
- finishing-a-development-branch-iddSkill
- greenfield-baselineSkill
- impacted-scope-enforcementSkill
- incremental-change-impactSkill
- incremental-deploymentSkill
- innersource-governance-bootstrapSkill
- issue-driven-deliverySkill
- library-extraction-stabilisationSkill
- local-dev-experienceSkill
- markdown-authorSkill
- modern-csharp-coding-standardsSkill
- monorepo-orchestration-setupSkill
- observability-logging-baselineSkill
- pair-programmingSkill
- persona-switchingSkill
- process-skill-routerSkill
- quality-gate-enforcementSkill
- release-tagging-planSkill
- repo-best-practices-bootstrapSkill
- repository-foundation-bootstrapSkill
- requirements-gatheringSkill
- runtime-tooling-validationSkill
- safe-brownfield-refactorSkill
- scoped-colocationSkill
- security-processesSkill
- selective-build-testSkill
- semantic-version-impactSkill
- session-awareSkill
- static-analysis-securitySkill
- structured-review-workflowSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 15 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Default behaviour for all repository work
- Very specific: line 52
Use process-skill-router to select the correct skill based on context
- Distinctive: line 64
AutoFix mechanism: When verification fails, AutoFix reads prerequisite repository URLs from AGENTS.md, fetches installation instructions …
- Distinctive: line 82
When creating a new repository:
- Distinctive: line 84
Create AGENTS.md with skills-first directives
- Distinctive: line 85
Create README.md with Work Items section
- Distinctive: line 87
Commit as part of repository setup
- Distinctive: line 93
When migrating existing repository:
- Very specific: line 95
Create feature branch: feat/add-skills-first-workflow
- Distinctive: line 97
Update README.md if needed (add Work Items section)
- Distinctive: line 99
Create PR if required
- Distinctive: line 140
Write failing tests before implementation
- Distinctive: line 145
Verify before claiming complete
- Distinctive: line 245
No manual intervention required for standard cases
- Distinctive: line 256
Use this script to verify all prerequisites are met:
- Distinctive: line 394
When validation fails, AutoFix performs these actions:
- Distinctive: line 441
Before proceeding with any task, verify:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skills-First-Workflow
Overview
Enforce that all work follows a skills-first approach: prerequisite skill libraries must be installed, bootstrapped, and loaded before any implementation begins. Performs runtime verification and automatically fixes missing prerequisites.
CRITICAL: Load this skill FIRST when entering any repository.
When to Use
Entering a repository:
- First action in any repository
- Beginning any task or work session
- Default behaviour for all repository work
Creating a repository:
- Initializing a new repository
- Scaffolding a new project
- Setting up repo structure
Migrating a repository:
- Adding skills-first workflow to existing repo
- Updating repository to enforce prerequisite loading
- Establishing skills-first practices
Core Workflow
- Announce the skill and confirm Superpowers availability.
- Verify prerequisites (runs automatically with AutoFix):
- Superpowers installed and bootstrapped
superpowers:using-superpowersloaded- AGENTS.md exists and references skills-first-workflow
- Task-relevant process skills loaded
- Initialize or migrate repository if needed:
- Greenfield: Create AGENTS.md and README.md
- Brownfield: Create AGENTS.md on feature branch
- Enforce process skills before implementation:
- Use
process-skill-routerto select the correct skill based on context - Process skills have precondition guards - check these before proceeding
- Brainstorming (for unclear requirements/new features)
- Planning (for multi-step tasks)
- TDD (for code changes)
- Verification (always before claiming complete)
- Use
- Block implementation until all verifications pass.
Runtime Verification
Prerequisites Checked
AutoFix mechanism: When verification fails, AutoFix reads prerequisite repository URLs from AGENTS.md, fetches installation instructions from source repositories, and executes per the agent's default installation mechanism. If AutoFix cannot complete automatically, it halts and provides manual instructions.
- Superpowers available → AutoFix: Install and bootstrap if not
- using-superpowers loaded → AutoFix: Load if not
- AGENTS.md exists → AutoFix: Create/update if not
- Task skills loaded → AutoFix: Load required skills if not
Verification must pass before any implementation work begins.
See references/AUTOFIX.md for detailed AutoFix procedures and examples.
Repository Initialization
Greenfield
When creating a new repository:
- Create AGENTS.md with skills-first directives
- Create README.md with Work Items section
- Verify initialization complete
- Commit as part of repository setup
See references/AGENTS-TEMPLATE.md for AGENTS.md content.
Brownfield
When migrating existing repository:
- Create feature branch:
feat/add-skills-first-workflow - Create AGENTS.md with skills-first directives
- Update README.md if needed (add Work Items section)
- Commit with evidence
- Create PR if required
See references/AGENTS-TEMPLATE.md for AGENTS.md content.
Strict Enforcement Rules
Before Implementation
All verifications must pass:
- Superpowers available
using-superpowersloaded- AGENTS.md exists and current
- Task-relevant skills loaded
Only then can implementation begin.
Process Skills Required
Use process-skill-router when uncertain which skill applies. The router evaluates
context and recommends the correct skill based on priority order.
Precondition guards: Process skills have precondition checks that must pass before
proceeding. If a precondition fails, the skill will redirect to the correct alternative.
For example, requirements-gathering checks that no ticket exists before proceeding.
For no ticket exists (new work):
- Load and apply
requirements-gatheringfirst to create a ticket
For unclear requirements or new features:
- Load and apply
superpowers:brainstormingfirst
For multi-step tasks:
- Load and apply
superpowers:writing-plansfirst
For code changes:
- Load and apply
superpowers:test-driven-developmentfirst - Write failing tests before implementation
For all tasks:
- Load and apply
superpowers:verification-before-completion - Verify before claiming complete
No Exceptions
User requests to skip:
- Explain cannot skip skills-first workflow
- Offer to streamline if skills already loaded
- Proceed with verification anyway
Simple changes (typos, formatting):
- Still verify skills loaded (fast if already met)
- Enforcement applies to all changes
Emergency hotfix:
- Skills-first still applies
- Minimal skill set acceptable (TDD + verification)
- Cannot skip verification entirely
Composition
This skill does NOT create rigid dependencies:
- Other skills do not declare this as prerequisite
- Loaded first by convention (via AGENTS.md reference)
- Skills remain composable and independent
Verification responsibilities:
- Verifies
using-superpowersloaded - Verifies AGENTS.md references skills-first-workflow
- Other skills loaded based on task requirements
Evidence Requirements
Greenfield:
- AGENTS.md created with skills-first directives and prerequisite repo URLs
- README.md created with Work Items section
- Both files committed as part of initialization
Brownfield:
- Feature branch created
- AGENTS.md created/updated with skills-first directives and prerequisite repo URLs
- Changes committed with evidence
- PR created if required
Every Task:
- Verification passed: Superpowers available
- Verification passed: using-superpowers loaded
- Verification passed: AGENTS.md exists and current
- Verification passed: Task-relevant skills loaded
- Process skills applied before implementation
Quick Reference
| Scenario | Action | Result |
| New repo | Load skill → AutoFix creates files | AGENTS.md + README.md initialized |
| Existing repo | Load skill → AutoFix on branch | AGENTS.md created via PR |
| Missing Superpowers | AutoFix installs | Superpowers bootstrapped |
| Missing skills | AutoFix loads | Required skills loaded |
| Skip request | Explain + proceed with verification | Enforcement maintained |
Red Flags - STOP
- "Just skip the skills and implement quickly."
- "We don't need AGENTS.md for this repo."
- "I'll load skills after I start coding."
- "Tests can come later, implement first."
- "Verification is optional for small changes."
Success Criteria
Prerequisites met:
- Superpowers installed and bootstrapped
using-superpowersloaded- AGENTS.md exists and references skills-first-workflow
Process followed:
- Process skills loaded before implementation
- TDD applied for code changes
- Verification applied before claiming complete
No shortcuts:
- Implementation did not begin before skills loaded
- Tests written before implementation code
- Verification completed before claiming done
AutoFix worked:
- Missing prerequisites automatically installed
- Missing AGENTS.md automatically created
- No manual intervention required for standard cases
References
references/AGENTS-TEMPLATE.md- Template for creating AGENTS.mdreferences/AUTOFIX.md- Detailed AutoFix behaviour for each verification checkprocess-skill-router- Route to correct process skill based on contextrequirements-gathering- Example of precondition guard pattern
Prerequisite Validation Script
Use this script to verify all prerequisites are met:
#!/bin/bash
# validate-skills-first.sh
ERRORS=0
WARNINGS=0
echo "=== Skills-First Workflow Validation ==="
echo ""
# Check 1: Superpowers installed
echo "1. Checking Superpowers installation..."
if [ -d "$HOME/.claude/plugins/cache/superpowers-marketplace" ]; then
echo " ✓ Superpowers plugin directory exists"
else
echo " ✗ Superpowers not installed"
echo " Fix: Run 'npm install -g @anthropic/superpowers' or install via Claude settings"
((ERRORS++))
fi
# Check 2: AGENTS.md exists
echo ""
echo "2. Checking AGENTS.md..."
if [ -f "AGENTS.md" ]; then
echo " ✓ AGENTS.md exists"
# Check for skills-first reference
if grep -q "skills-first-workflow" AGENTS.md; then
echo " ✓ References skills-first-workflow"
else
echo " ⚠ Does not reference skills-first-workflow"
((WARNINGS++))
fi
# Check for prerequisite URLs
if grep -q "github.com" AGENTS.md; then
echo " ✓ Contains prerequisite repository URLs"
else
echo " ⚠ No prerequisite repository URLs found"
((WARNINGS++))
fi
else
echo " ✗ AGENTS.md not found"
echo " Fix: Create AGENTS.md from template"
((ERRORS++))
fi
# Check 3: README.md exists
echo ""
echo "3. Checking README.md..."
if [ -f "README.md" ]; then
echo " ✓ README.md exists"
else
echo " ✗ README.md not found"
((ERRORS++))
fi
# Check 4: Git repository
echo ""
echo "4. Checking git repository..."
if git rev-parse --git-dir > /dev/null 2>&1; then
echo " ✓ Git repository initialized"
# Check for remote
if git remote get-url origin > /dev/null 2>&1; then
echo " ✓ Remote 'origin' configured"
else
echo " ⚠ No remote configured"
((WARNINGS++))
fi
else
echo " ✗ Not a git repository"
((ERRORS++))
fi
# Summary
echo ""
echo "=== Summary ==="
echo "Errors: $ERRORS"
echo "Warnings: $WARNINGS"
if [ $ERRORS -eq 0 ]; then
echo ""
echo "✓ All prerequisites met - ready for skills-first workflow"
exit 0
else
echo ""
echo "✗ $ERRORS prerequisite(s) not met"
echo "Run AutoFix or manually resolve before proceeding"
exit 1
fiSample Verification Commands
Check Superpowers Status
# Check if Superpowers CLI is available
superpowers --version
# Check plugin installation location
ls -la ~/.claude/plugins/cache/superpowers-marketplace/
# Verify using-superpowers skill exists
ls ~/.claude/plugins/cache/superpowers-marketplace/superpowers/*/skills/using-superpowers/Check Repository Prerequisites
# Verify AGENTS.md content
cat AGENTS.md | head -50
# Check for required sections
grep -E "^#|skills-first" AGENTS.md
# Verify README.md exists and has content
wc -l README.mdValidate Skill Loading
# In Claude Code, verify skills loaded
# These commands show skill status in conversation
# Check if using-superpowers is active
# (Look for skill announcement in conversation)
# Verify process skills available
# (Use /skills command in Claude Code)AutoFix Command Examples
When validation fails, AutoFix performs these actions:
Missing AGENTS.md
# AutoFix creates AGENTS.md from template
cat > AGENTS.md << 'EOF'
# AGENTS.md - Skills-First Workflow
## Required Reading
Before ANY work in this repository, load: `development-skills:skills-first-workflow`
## Prerequisites
- Superpowers: https://github.com/anthropics/superpowers
- Development Skills: https://github.com/org/development-skills
## Process Skills
1. **requirements-gathering** - Before creating tickets
2. **brainstorming** - For unclear requirements
3. **writing-plans** - For multi-step tasks
4. **test-driven-development** - For code changes
5. **verification-before-completion** - Before claiming done
EOF
git add AGENTS.md
git commit -m "docs: add AGENTS.md for skills-first workflow"Missing Superpowers
# AutoFix installs Superpowers
# (Actual command depends on environment)
# For Claude Code:
# Settings > Extensions > Install Superpowers
# For CLI:
npm install -g @anthropic/superpowers
superpowers bootstrapEvidence Checklist
Before proceeding with any task, verify:
validate-skills-first.shexits with code 0- Superpowers plugin directory exists
- AGENTS.md contains skills-first-workflow reference
- README.md exists
- Git repository initialized with remote
# One-liner verification
./validate-skills-first.sh && echo "Ready to proceed"Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

