feature-spec

Feature specification and planning guidelines for software engineers. This skill should be used when writing PRDs, defining requirements, managing scope, prioritizing features, or handling change requests. Triggers on tasks involving feature planning, specification writing, stakeholder alignment, or scope management.

Ir para a instalação

Repositório: pproenca/dot-skills
Última atividade na origem: 27 de maio de 2026 às 09:50
Idioma detectado do SKILL.md: inglês
Estrelas: 194
Forks: 17

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/pproenca/dot-skills --skill feature-spec

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

48 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

drizzle-nextjs-postgres

Drizzle ORM against PostgreSQL inside a Next.js App Router app. Covers client construction (globalThis singleton across HMR, serverless pool sizing, `prepare:false` behind PgBouncer/Supavisor, driver choice when you need interactive transactions, `server-only`), reads in Server Components under Next.js 16 Cache Components (`use cache` superseding `unstable_cache` and the `revalidate`/`dynamic` segment configs, Suspense boundaries, React `cache()` dedupe), Server Actions (authorization inside the action, `updateTag` vs `revalidateTag`, `after()`), Postgres schema types (timestamptz, identity vs serial, jsonb, numeric-as-string, bigint modes), drizzle-kit migrations (generate vs push, CONCURRENTLY outside the migrator, NOT VALID constraints, rename prompts), transactions and pooled connections, and Postgres query traps (keyset pagination, count cost, driver-dependent `db.execute()` shape, NOT IN nulls, prepared statements). Use when writing or reviewing Drizzle + Postgres code in Next.js.

2026-07-24

relational-data-modeling

Corrects the wrong defaults a model has when designing a relational schema — the DDL decisions an experienced engineer makes differently. Use when creating or reviewing tables, migrations, ER models, or ORM schema definitions. Covers identity and keys (surrogate vs natural, identity vs serial, uuidv7, composite keys that make cross-tenant references impossible), relationships (polymorphic foreign keys the database cannot enforce, referential actions, unindexed FK columns, disjoint subtypes), invariants the engine can prove instead of application code (EXCLUDE, partial unique indexes, CHECK limits, deferrable cycles, NOT VALID), types (timestamptz, exact money, range types, enum vs lookup table), derived and encoded data (generated columns, JSONB as an escape hatch), and time (events vs in-place updates, soft-delete flags that silently disable constraints, temporal keys). NOT for query tuning, index selection for read paths, or connection pooling.

2026-07-23

relational-database-design

Distills a logical relational-database design methodology into rules an agent applies while designing or reviewing a schema. Covers the design sequence (mission → tables → fields → keys → relationships → business rules → views → integrity review), one-subject-per-table decomposition, atomic single-valued fields, candidate/primary/foreign keys, relationship types with deletion rules and participation, the four levels of data integrity, database-vs-application business rules, validation tables, views for derived data, and the flat-file / spreadsheet / RDBMS-driven antipatterns to avoid. The structure is logical and RDBMS-agnostic, and normalized by construction. Use when designing a new relational schema, reviewing or refactoring an existing one, resolving redundant or repeating data, choosing keys, modeling relationships, or deciding where a constraint belongs.

2026-07-23

Ver todas deste repositório

name	feature-spec
description	Feature specification and planning guidelines for software engineers. This skill should be used when writing PRDs, defining requirements, managing scope, prioritizing features, or handling change requests. Triggers on tasks involving feature planning, specification writing, stakeholder alignment, or scope management.

Software Engineering Feature Specification and Planning Best Practices

Comprehensive feature specification and planning guide for software engineers, product managers, and technical leads. Contains 42 rules across 8 categories, prioritized by impact to prevent scope creep and ensure project success.

When to Apply

Reference these guidelines when:

Writing PRDs or feature specifications
Defining requirements or user stories
Managing scope and preventing scope creep
Prioritizing features and backlog items
Handling change requests
Aligning stakeholders on project goals

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Scope Definition	CRITICAL	`scope-`
2	Requirements Clarity	CRITICAL	`req-`
3	Prioritization Frameworks	HIGH	`prio-`
4	Acceptance Criteria	HIGH	`accept-`
5	Stakeholder Alignment	MEDIUM-HIGH	`stake-`
6	Technical Specification	MEDIUM	`tech-`
7	Change Management	MEDIUM	`change-`
8	Documentation Standards	LOW	`doc-`

Quick Reference

1. Scope Definition (CRITICAL)

scope-define-boundaries - Define explicit scope boundaries
scope-document-assumptions - Document all assumptions explicitly
scope-work-breakdown - Break scope into measurable work items
scope-define-mvp - Define MVP before full feature set
scope-stakeholder-signoff - Get stakeholder signoff on scope

2. Requirements Clarity (CRITICAL)

req-specific-measurable - Write specific, measurable requirements
req-user-stories - Structure requirements as user stories
req-avoid-solution-language - Avoid solution-specific language
req-functional-nonfunctional - Separate functional and non-functional
req-consistent-terminology - Use consistent terminology
req-traceability - Maintain requirements traceability

3. Prioritization Frameworks (HIGH)

prio-moscow-method - Use MoSCoW prioritization method
prio-rice-scoring - Apply RICE scoring for objectivity
prio-value-vs-effort - Map value vs effort explicitly
prio-dependencies-first - Identify and order dependencies
prio-kano-model - Apply Kano model for feature classification

4. Acceptance Criteria (HIGH)

accept-given-when-then - Use Given-When-Then format
accept-testable-criteria - Write testable acceptance criteria
accept-edge-cases - Include edge cases in acceptance
accept-definition-of-done - Define clear definition of done
accept-avoid-over-specification - Avoid over-specification

5. Stakeholder Alignment (MEDIUM-HIGH)

stake-identify-stakeholders - Identify all stakeholders early
stake-early-feedback - Gather feedback early and often
stake-conflict-resolution - Resolve conflicts explicitly
stake-communication-plan - Establish communication cadence
stake-success-metrics - Align on success metrics

6. Technical Specification (MEDIUM)

tech-system-context - Document system context and dependencies
tech-api-contracts - Define API contracts before implementation
tech-data-model - Specify data models and schema changes
tech-error-handling - Plan error handling and recovery
tech-performance-requirements - Specify performance requirements
tech-security-considerations - Document security considerations

7. Change Management (MEDIUM)

change-formal-process - Use formal change request process
change-impact-assessment - Assess full impact before approval
change-version-tracking - Version all specification documents
change-scope-freeze - Implement scope freeze periods
change-defer-log - Maintain deferred items log

8. Documentation Standards (LOW)

doc-single-source - Maintain single source of truth
doc-consistent-templates - Use consistent document templates
doc-decision-records - Document key decisions with context
doc-accessible-format - Keep documentation accessible
doc-glossary-terms - Define project terminology

feature-spec

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Software Engineering Feature Specification and Planning Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Scope Definition (CRITICAL)

2. Requirements Clarity (CRITICAL)

3. Prioritization Frameworks (HIGH)

4. Acceptance Criteria (HIGH)

5. Stakeholder Alignment (MEDIUM-HIGH)

6. Technical Specification (MEDIUM)

7. Change Management (MEDIUM)

8. Documentation Standards (LOW)

Mais deste repositório

Software Engineering Feature Specification and Planning Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Scope Definition (CRITICAL)

2. Requirements Clarity (CRITICAL)

3. Prioritization Frameworks (HIGH)

4. Acceptance Criteria (HIGH)

5. Stakeholder Alignment (MEDIUM-HIGH)

6. Technical Specification (MEDIUM)

7. Change Management (MEDIUM)

8. Documentation Standards (LOW)