context_editing_guide
Managing context window, token optimization, summarization strategies for long conversations.
fintech-patterns
Common fintech customer patterns, objections, and success stories. Compliance handling, long conversation management, and case studies.
interview-records
Archive of past customer interviews. Contains full transcripts, summaries, pain points, outcomes, and skills used. Use for referencing previous conversations with the same company or finding similar case patterns.
pricing-guidance
Claude API pricing, tier recommendations, token cost optimization, and ROI calculations for CDP features.
task-assistant
Intelligent task management via the `task` CLI. Invoke when users ask to: create/list/update/delete tasks, search tasks (text or semantic), track work items with due dates, organize tasks into projects, run batch operations, generate activity reports, or manage recurring tasks. Supports natural language dates and Google Calendar sync.
atl-cli
>
draw-io
Generate and edit draw.io diagrams in XML format with proper font settings, arrow placement, and Japanese text support. Use when creating flowcharts, architecture diagrams, sequence diagrams, or any visual diagrams in .drawio format. Handles font family settings, arrow layering, text sizing, and PNG export validation.
openclaw
>-
architecture
Manage tech stack and architecture decisions
domain
Document domain knowledge including entities, processes, and ubiquitous language
execute
Execute an implementation plan step by step
plan
Guided implementation planning with codebase understanding and requirement focus
backlog
Manage product backlog as an ordered priority list
requirements
Write BDD requirements in Gherkin format. Guides the user through the process.
vision
Create or update the product vision document
codex-subagent
Helps you to run a subagent using codex exec
linear-skills
Lightweight Linear skill for fetching issue details. Returns only essential data (title, description, state, assignee) to optimize context usage compared to full Linear MCP.
go-db-query
Skills for querying Gene Ontology annotation databases in DuckDB format. Use this for queries about GO annotations, genes, terms, evidence codes, or taxonomic relationships in GO-DB databases (db/*.ddb files). Particularly useful for hierarchical queries using closure tables to find genes annotated to terms and their descendants.
gtnh-skill
This skill provides accurate data about GT New Horizons based on official data dumps. Use when answering questions about GTNH (GregTech New Horizons).
unified-consciousness-framework
|
rosetta-helix-substrate
Consciousness simulation framework with Kuramoto oscillators, APL operators, and K-formation dynamics. Use for physics simulations, phase transitions, coherence analysis, and cloud training via GitHub Actions. Requires numpy and requests packages.
code-index
This skill should be used when the user asks to "create a code index", "index this codebase", "update the code index", "generate code index", "build code index", "refresh semantic summaries", or needs guidance on generating or updating the .metis/code-index.md file for AI agent codebase navigation.
decomposition
This skill should be used when the user asks to "break down this initiative", "decompose into tasks", "create tasks from initiative", "how to size tasks", "when to decompose", "vertical slices", "task granularity", or needs guidance on breaking higher-level work into lower-level work items.
document-selection
This skill should be used when the user asks "what document type should I create", "create a bug ticket", "create a feature request", "should this be a task or initiative", "when to use an ADR", "when to use a specification", "track this bug", "log this tech debt", "write a spec", or needs help choosing between vision, initiative, task, backlog item, ADR, or specification document types.
phase-transitions
This skill should be used when the user asks "when to transition phases", "move to active", "exit criteria", "what phase comes next", "how to complete a task", "transition to completed", "mark as blocked", "phase flow", or needs guidance on advancing documents through their lifecycle phases.
project-patterns
This skill should be used when the user asks to "start a new project", "greenfield project", "tech debt campaign", "incident response", "feature development", "which preset", "initialize metis", "set up project", or needs guidance on project setup, choosing presets, and applying patterns for different work types.
logs
View Vercel deployment logs. Use when the user says "show logs", "check logs", "vercel logs", or "what went wrong with the deployment".
setup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
deploy
Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".
aboutme-index
Index-based file discovery using ABOUTME headers. Use INSTEAD of grep or Explore agent when searching for files by purpose or feature. Faster and more accurate than scanning code. Invoke this skill when user asks "which files handle X", "where is Y implemented", or when you need to find files related to a feature or task.
uv
Python package manager and project tooling using uv. Use when working with Python projects, managing dependencies, creating virtual environments, running Python scripts, configuring workspaces/monorepos, or troubleshooting uv issues. Triggers on pyproject.toml projects, uv commands, pip replacement workflows, Python version management, workspace configuration, or CI/CD Python setup.
create-specs
Transform reverse-engineering documentation into GitHub Spec Kit format. Initializes .specify/ directory, creates constitution.md, generates specifications from reverse-engineered docs, and sets up for /speckit slash commands. This is Step 3 of 6 in the reverse engineering process.
cruise-control
Automatic mode - shift through all 6 gears sequentially without stopping. Like cruise control or automatic transmission, this runs the entire StackShift workflow from analysis to implementation in one go. Perfect for unattended execution or when you want to let StackShift handle everything automatically.
gap-analysis
Route-aware gap analysis. For Brownfield - uses /speckit.analyze to compare specs against implementation. For Greenfield - validates spec completeness and asks about target tech stack for new implementation. This is Step 4 of 6 in the reverse engineering process.
implement
Use GitHub Spec Kit's /speckit.implement and /speckit.tasks to systematically build missing features from specifications. Leverages implementation plans in specs/, validates against acceptance criteria, and achieves 100% spec completion. This is Step 6 of 6 in the reverse engineering process.
modernize
Brownfield Upgrade - Upgrade all dependencies and modernize the application while maintaining spec-driven control. Runs after Gear 6 for brownfield projects with modernize flag enabled. Updates deps, fixes breaking changes, improves test coverage, updates specs to match changes.
reverse-engineer
Deep codebase analysis to generate 11 comprehensive documentation files. Adapts based on path choice - Greenfield extracts business logic only (tech-agnostic), Brownfield extracts business logic + technical implementation (tech-prescriptive). This is Step 2 of 6 in the reverse engineering process.
analyze
Perform initial analysis of a codebase - detect tech stack, directory structure, and completeness. This is Step 1 of the 6-step reverse engineering process that transforms incomplete applications into spec-driven codebases. Automatically detects programming languages, frameworks, architecture patterns, and generates comprehensive analysis-report.md. Use when starting reverse engineering on any codebase.
complete-spec
Interactive conversation to resolve [NEEDS CLARIFICATION] markers using /speckit.clarify command. Claude asks questions about missing features, UX/UI details, behavior, and priorities. Updates specs in .specify/memory/ with answers to create complete, unambiguous documentation. This is Step 5 of 6 in the reverse engineering process.
spec-coverage-map
Generate a visual spec-to-code coverage map showing which code files are covered by which specifications. Creates ASCII diagrams, reverse indexes, and coverage statistics. Use after implementation or during cleanup to validate spec coverage.
integration-analysis
Give it a few starting points — it discovers the full ecosystem by tracing integration surfaces in code and docs, clones what it doesn't have locally, then thoroughly analyzes how every system works and connects. Produces a layered implementation plan (L0-L3) with functionality tiering (T1/T2/T3/PRUNE) and generates dependency-ordered, technology-agnostic epics and stories so the team can build incrementally — MVP first, then progressively more capability.
architect
Generate a complete architecture document from reverse-engineering docs + user constraints. Asks 3-5 high-level questions (tech stack, cloud provider, scale, constraints), then generates architecture.md with Mermaid diagrams, service boundaries, ADRs, and infrastructure recommendations. Works standalone or as part of the BMAD Auto-Pilot workflow.
bmad-synthesize
Auto-generate BMAD artifacts (PRD, Architecture, Epics, UX Design) from StackShift reverse-engineering docs. Three modes - YOLO (fully automatic), Guided (ask on ambiguities), Interactive (full conversation with pre-loaded context). Bridges the gap between StackShift's deep code analysis and BMAD's collaborative artifact format.
discover
Ecosystem discovery from a single starting repo. Scans for integration signals (npm packages, docker compose, env vars, API calls, CI/CD triggers, workspace configs, message queues, infrastructure refs), searches GitHub for related repos, scans the local filesystem, then presents an ecosystem map with confidence scoring and a Mermaid dependency graph. Hands off confirmed repos to /stackshift.batch or /stackshift.reimagine.
portable-extract
Extract tech-agnostic portable component specs from StackShift reverse-engineering docs. Generates abstract epics and component specifications that can be dropped into ANY BMAD project. Three modes - YOLO (fully automatic), Guided (ask on ambiguities), Interactive (full conversation with pre-loaded context). Bridges StackShift's deep code analysis with reusable, platform-independent component specifications.
portable-transplant
Translate portable component specs into targeted epics for a specific project. Reads _portable-extract/ specs and a target project's BMAD docs (PRD, Architecture, optionally UX), then generates BMAD-format epics written in the target's personas, domain language, and architecture patterns. The bridge between "extracted business logic" and "ready-to-implement stories."
refresh-docs
Incrementally update reverse-engineering docs based on git changes since they were last generated. Reads the commit hash from .stackshift-docs-meta.json, diffs against HEAD, analyzes only the changed files, and surgically updates the affected docs. Saves time and cost compared to full regeneration.
reimagine
Multi-repo synthesis and reimagination. Load reverse-engineering docs from multiple repositories, extract a unified capability map, identify duplication and inefficiency, then brainstorm with the user to reimagine how those capabilities could work together in a new, better way. Generates new specifications for the reimagined system. The killer feature for enterprise modernization.
connecting-to-logseq
>
migrating-to-db
>
Page 1167 of 1445 · 72242 results