Evolutionary-Leadership
Official@Evolutionary-Leadership
Evolutionary-Leadership provides a gated software delivery skill suite covering feature specification, TDD implementation, code review, releases, hotfixes, and rollbacks on GitHub and Railway.
Agent Skills by Evolutionary-Leadership
Showing 28 vetted skills indexed across 1 GitHub repositories.
hotfix
Creates an emergency hotfix branch from main and triggers a fast-track patch release to production.
release
Ship preprod to production by creating a release PR, version tag, and GitHub Release.
status
Displays a team dashboard of active feature branches, open PRs, preview URLs, and release status.
getting-started
Orients Claude Code sessions by listing available skills, agents, and workflow rules.
review
Creates a non-auto-merging pull request from a feature branch to preprod for human review.
feature
Drives a feature from description to merged-ready code through five gated phases.
continue
Resumes in-progress feature branches with their committed context and preview URLs.
mcp-tool
Adds, modifies, or removes tools on an OAuth-authorized MCP server endpoint.
domain-modeling
Maintains project domain vocabulary in a glossary and records architectural decisions as ADRs.
endchat
Deletes orphaned feature and claude branches after a chat session and returns the checkout to preprod.
chat
Discuss ideas and research topics without modifying the repository.
brainstorm
Interviews users to stress-test ideas and records outcomes in issue tracker.
writing-for-agents
Guides writing skills, AGENTS.md, and CLAUDE.md documents for predictable agent behavior.
to-preprod
Triggers auto-merge of a feature branch into preprod via a signal file and GitHub Actions.
changelog
Generates CHANGELOG.md entries from merged pull requests since the last release tag.
diagnosing-bugs
Diagnose hard bugs and performance regressions through a structured six-phase feedback-loop workflow.
code-review
Reviews git diffs against coding standards and specifications using parallel sub-agents.
to-tickets
Breaks specs and plans into tracer-bullet tickets with blocking edges published to the issue tracker.
setup
Configures a fresh Harness template repository by choosing Railway or code-only variants and pushing one commit.
to-spec
Synthesizes conversation context into a published specification with conflict sweep and proposals.
codebase-design
Designs deep modules with small interfaces, clean seams, and testable adapters.
document
Writes and audits project documentation against an AI-native docs standard.
implement
Implements tickets from a spec by working the unblocked frontier with TDD and reporting.
deps
Review and batch-merge Dependabot pull requests grouped by risk level.
Frequently Asked Questions About Evolutionary-Leadership
FAQPage SchemaWhat tasks can I automate using Evolutionary-Leadership's skills?▼
You can run gated feature development (brainstorm, spec, tickets, implement, review), ship releases with version tags and GitHub Releases, apply emergency hotfixes with patch tagging, roll back production to a prior release tag, generate changelogs from merged PRs, triage Dependabot PRs by risk, and diagnose bugs or performance regressions.
Who are these skills designed for?▼
Software engineers and technical leads working in a GitHub-based trunk-to-preprod-to-production branching model, particularly teams deploying to Railway who want disciplined phase gates: specification before implementation, test-driven development, dual-axis code review, and controlled release and rollback procedures.
How do the release and hotfix skills work in practice?▼
The release skill ships preprod to production by opening a release PR, tagging a major, minor, or patch version, and generating a GitHub Release; Railway redeploys automatically. The hotfix skill branches from main, merges the fix PR, auto-tags a patch release, and back-merges to preprod.
What prerequisites and dependencies do these skills require?▼
Skills invoke git and the GitHub CLI (gh), Node and Python doc-checking scripts, pnpm, and curl. Some skills use GitHub MCP operations such as push_files and pull request reads. The setup skill configures a fresh template with optional Railway deployment, a pre-built technical foundation, and MCP access.
How does the feature skill enforce quality before implementation?▼
The feature skill runs gated phases: it captures the change, grills the rationale and approach via an interview engine, writes and publishes a specification, breaks it into tracer-bullet tickets with declared blocking edges, then implements ticket by ticket, ending with parallel standards-and-spec code review sub-agents.