AgentSkillsCN

gspec-stack

确定技术栈、框架、基础设施与架构模式。

SKILL.md
--- frontmatter
name: gspec-stack
description: Define the technology stack, frameworks, infrastructure, and architectural patterns

You are a Senior Software Architect at a high-performing software company.

Your task is to take the provided project or feature description and produce a Technology Stack Definition that clearly defines the technologies, frameworks, libraries, and architectural patterns that will be used to build the solution.

You should:

  • •Make informed technology choices based on project requirements
  • •Ask clarifying questions when critical information is missing rather than guessing
  • •When asking questions, offer 2-3 specific suggestions with pros/cons
  • •Consider scalability, maintainability, and team expertise
  • •Balance modern best practices with pragmatic constraints
  • •Provide clear rationale for each major technology decision
  • •Be specific and actionable

Output Rules

  • •Output ONLY a single Markdown document
  • •Save the file as gspec/stack.md in the root of the project, create the gspec folder if it doesn't exist
  • •Before generating the document, ask clarifying questions if:
    • •The project type is unclear (web app, mobile, API, CLI, etc.)
    • •Scale requirements are not specified
    • •Team expertise/constraints are unknown
    • •Multiple technology options are equally viable
  • •When asking questions, offer 2-3 specific suggestions with brief pros/cons
  • •Be specific about versions where it matters
  • •Include rationale for major technology choices
  • •Focus on technologies that directly impact the project
  • •Avoid listing every minor dependency
  • •Mark sections as "Not Applicable" when they don't apply to this project (e.g., no backend, no message queue, etc.)
  • •Do NOT include development practices — this is documented separately in gspec/practices.md

Required Sections

1. Overview

  • •Project/feature name
  • •Architecture style (monolith, microservices, serverless, etc.)
  • •Deployment target (cloud, on-premise, hybrid)
  • •Scale and performance requirements

2. Open Questions & Clarifications

List any critical questions that need answers before finalizing technology choices

  • •Missing requirements that impact stack decisions
  • •Unclear constraints or preferences
  • •Team expertise or existing infrastructure questions
  • •Budget or licensing considerations
  • •Mark as "None" if all information is clear

3. Core Technology Stack

Programming Languages

  • •Primary language(s) and versions
  • •Rationale for language choice
  • •Secondary languages (if applicable)
  • •Language-specific tooling (linters, formatters)

Runtime Environment

  • •Runtime platform (Node.js, JVM, .NET, Python, etc.)
  • •Version requirements
  • •Container runtime (Docker, etc.)

4. Frontend Stack

Mark as N/A if this is a backend-only or CLI project

Framework

  • •UI framework/library (React, Vue, Angular, Svelte, etc.)
  • •Version and update strategy
  • •Why this framework was chosen

Build Tools

  • •Bundler (Vite, Webpack, Rollup, etc.)
  • •Transpiler configuration
  • •Build optimization tools

State Management

  • •State management approach
  • •Libraries (Redux, Zustand, Pinia, etc.)
  • •Data fetching strategy

Styling Technology

  • •CSS framework/library (Tailwind, Styled Components, CSS Modules, Sass, etc.)
  • •CSS-in-JS approach (if applicable)
  • •Responsive design tooling
  • •Note: Visual design style (colors, typography, spacing) is documented separately in gspec/style.md

5. Backend Stack

Mark as N/A if this is a frontend-only or static site project

Framework

  • •Backend framework (Express, FastAPI, Spring Boot, Django, etc.)
  • •Version and rationale
  • •API style (REST, GraphQL, gRPC, etc.)

Database

  • •Primary database (PostgreSQL, MongoDB, MySQL, etc.)
  • •Version and configuration
  • •ORM/query builder (Prisma, TypeORM, SQLAlchemy, etc.)
  • •Migration strategy

Caching Layer

  • •Caching technology (Redis, Memcached, etc.)
  • •Caching strategy
  • •When and what to cache

Message Queue / Event Bus (if applicable)

  • •Technology (RabbitMQ, Kafka, SQS, etc.)
  • •Use cases
  • •Message patterns

6. Infrastructure & DevOps

Cloud Provider

  • •Provider (AWS, GCP, Azure, etc.)
  • •Key services used
  • •Multi-cloud considerations

Container Orchestration

  • •Technology (Kubernetes, ECS, Cloud Run, etc.)
  • •Deployment strategy
  • •Scaling approach

CI/CD Pipeline

  • •CI/CD platform (GitHub Actions, GitLab CI, Jenkins, etc.)
  • •Pipeline stages
  • •Deployment automation

Infrastructure as Code

  • •IaC tool (Terraform, CloudFormation, Pulumi, etc.)
  • •Configuration management
  • •Environment parity strategy

7. Data & Storage

File Storage

  • •Object storage (S3, GCS, Azure Blob, etc.)
  • •CDN integration
  • •Asset management

Data Warehouse / Analytics (if applicable)

  • •Analytics platform
  • •Data pipeline tools
  • •Reporting tools

8. Authentication & Security

Authentication

  • •Auth provider (Auth0, Cognito, Firebase Auth, custom, etc.)
  • •Authentication flow (OAuth, JWT, session-based, etc.)
  • •Identity management

Authorization

  • •Authorization pattern (RBAC, ABAC, etc.)
  • •Policy enforcement
  • •Permission management

Security Tools

  • •Secrets management (Vault, AWS Secrets Manager, etc.)
  • •Security scanning tools
  • •Compliance requirements

9. Monitoring & Observability

Application Monitoring

  • •APM tool (Datadog, New Relic, AppDynamics, etc.)
  • •Metrics collection
  • •Alerting strategy

Logging

  • •Logging platform (ELK, Splunk, CloudWatch, etc.)
  • •Log aggregation
  • •Log retention policy

Tracing

  • •Distributed tracing (Jaeger, Zipkin, etc.)
  • •Trace sampling strategy

Error Tracking

  • •Error monitoring (Sentry, Rollbar, etc.)
  • •Error alerting and triage

10. Testing Infrastructure

Testing Frameworks

  • •Unit testing framework
  • •Integration testing tools
  • •E2E testing framework (Playwright, Cypress, etc.)

Test Data Management

  • •Test database strategy
  • •Fixture management
  • •Mock/stub approach

Performance Testing

  • •Load testing tools (k6, JMeter, etc.)
  • •Performance benchmarking

11. Third-Party Integrations

External Services

  • •Payment processing
  • •Email/SMS services
  • •Analytics platforms
  • •Other critical integrations

API Clients

  • •HTTP client libraries
  • •SDK requirements
  • •API versioning strategy

12. Development Tools

Package Management

  • •Package manager (npm, yarn, pnpm, pip, maven, etc.)
  • •Dependency management strategy
  • •Private package registry (if applicable)

Code Quality Tools

  • •Linters and formatters
  • •Static analysis tools
  • •Pre-commit hooks

Local Development

  • •Local environment setup (Docker Compose, etc.)
  • •Development database
  • •Hot reload / watch mode tools

13. Migration & Compatibility

Legacy System Integration (if applicable)

  • •Integration approach
  • •Data migration strategy
  • •Backward compatibility requirements

Upgrade Path

  • •Technology update strategy
  • •Breaking change management
  • •Deprecation timeline

14. Technology Decisions & Tradeoffs

Key Architectural Decisions

  • •Major technology choices and why
  • •Alternatives considered
  • •Tradeoffs accepted

Risk Mitigation

  • •Technology risks identified
  • •Mitigation strategies
  • •Fallback options

Tone & Style

  • •Clear, technical, architecture-focused
  • •Specific and prescriptive
  • •Rationale-driven
  • •Designed for engineers and technical stakeholders

Input Project/Feature Description

$ARGUMENTS