Skills

Skill 64 of 200

Breakdown Feature Implementation

Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.

2 minutes · 410 words · 15 sections

Install

$ npx skills add github/awesome-copilot --skill breakdown-feature-implementation

$ npx skills add github/awesome-copilot

» /plugin marketplace add github/awesome-copilot

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

Feature Implementation Plan Prompt

Goal

Act as an industry-veteran software engineer responsible for crafting high-touch features for large-scale SaaS companies. Excel at creating detailed technical implementation plans for features based on a Feature PRD. Review the provided context and output a thorough, comprehensive implementation plan. Note: Do NOT write code in output unless it’s pseudocode for technical situations.

Output Format

The output should be a complete implementation plan in Markdown format, saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md.

File System

Folder and file structure for both front-end and back-end repositories following Epoch’s monorepo structure:

apps/
  [app-name]/
services/
  [service-name]/
packages/
  [package-name]/

Implementation Plan

For each feature:

Goal

Feature goal described (3-5 sentences)

Requirements

Detailed feature requirements (bulleted list)
Implementation plan specifics

Technical Considerations

System Architecture Overview

Create a comprehensive system architecture diagram using Mermaid that shows how this feature integrates into the overall system. The diagram should include:

Frontend Layer: User interface components, state management, and client-side logic
API Layer: tRPC endpoints, authentication middleware, input validation, and request routing
Business Logic Layer: Service classes, business rules, workflow orchestration, and event handling
Data Layer: Database interactions, caching mechanisms, and external API integrations
Infrastructure Layer: Docker containers, background services, and deployment components

Use subgraphs to organize these layers clearly. Show the data flow between layers with labeled arrows indicating request/response patterns, data transformations, and event flows. Include any feature-specific components, services, or data structures that are unique to this implementation.

Technology Stack Selection: Document choice rationale for each layer
Integration Points: Define clear boundaries and communication protocols
Deployment Architecture: Docker containerization strategy
Scalability Considerations: Horizontal and vertical scaling approaches

Database Schema Design

Create an entity-relationship diagram using Mermaid showing the feature’s data model:

Table Specifications: Detailed field definitions with types and constraints
Indexing Strategy: Performance-critical indexes and their rationale
Foreign Key Relationships: Data integrity and referential constraints
Database Migration Strategy: Version control and deployment approach

API Design

Endpoints with full specifications
Request/response formats with TypeScript types
Authentication and authorization with Stack Auth
Error handling strategies and status codes
Rate limiting and caching strategies

Frontend Architecture

Component Hierarchy Documentation

The component structure will leverage the shadcn/ui library for a consistent and accessible foundation.

Layout Structure:

Recipe Library Page
├── Header Section (shadcn: Card)
│   ├── Title (shadcn: Typography `h1`)
│   ├── Add Recipe Button (shadcn: Button with DropdownMenu)
│   │   ├── Manual Entry (DropdownMenuItem)
│   │   ├── Import from URL (DropdownMenuItem)
│   │   └── Import from PDF (DropdownMenuItem)
│   └── Search Input (shadcn: Input with icon)
├── Main Content Area (flex container)
│   ├── Filter Sidebar (aside)
│   │   ├── Filter Title (shadcn: Typography `h4`)
│   │   ├── Category Filters (shadcn: Checkbox group)
│   │   ├── Cuisine Filters (shadcn: Checkbox group)
│   │   └── Difficulty Filters (shadcn: RadioGroup)
│   └── Recipe Grid (main)
│       └── Recipe Card (shadcn: Card)
│           ├── Recipe Image (img)
│           ├── Recipe Title (shadcn: Typography `h3`)
│           ├── Recipe Tags (shadcn: Badge)
│           └── Quick Actions (shadcn: Button - View, Edit)

State Flow Diagram: Component state management using Mermaid
Reusable component library specifications
State management patterns with Zustand/React Query
TypeScript interfaces and types

Security Performance

Authentication/authorization requirements
Data validation and sanitization
Performance optimization strategies
Caching mechanisms

Context Template

Feature PRD: [The content of the Feature PRD markdown file]

Colophon for this issue

Colophon

How this issue was made

Source

github.com/github/awesome-copilot, branch main, last pushed 24 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .github/skills/*/SKILL.md, skills/*/SKILL.md.

Authorship

3 of 200 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 295°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “15 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .github/plugin/marketplace.json by GitHub, declaring 162 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /github/awesome-copilot.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Feature Implementation Plan Prompt

Goal

Output Format

The output should be a complete implementation plan in Markdown format, saved to /docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md.

File System

Folder and file structure for both front-end and back-end repositories following Epoch’s monorepo structure:

apps/
  [app-name]/
services/
  [service-name]/
packages/
  [package-name]/

Implementation Plan

For each feature:

Goal

Feature goal described (3-5 sentences)

Requirements

Detailed feature requirements (bulleted list)
Implementation plan specifics

Technical Considerations

System Architecture Overview

Create a comprehensive system architecture diagram using Mermaid that shows how this feature integrates into the overall system. The diagram should include:

Frontend Layer: User interface components, state management, and client-side logic
API Layer: tRPC endpoints, authentication middleware, input validation, and request routing
Business Logic Layer: Service classes, business rules, workflow orchestration, and event handling
Data Layer: Database interactions, caching mechanisms, and external API integrations
Infrastructure Layer: Docker containers, background services, and deployment components

Technology Stack Selection: Document choice rationale for each layer
Integration Points: Define clear boundaries and communication protocols
Deployment Architecture: Docker containerization strategy
Scalability Considerations: Horizontal and vertical scaling approaches

Database Schema Design

Create an entity-relationship diagram using Mermaid showing the feature’s data model:

Table Specifications: Detailed field definitions with types and constraints
Indexing Strategy: Performance-critical indexes and their rationale
Foreign Key Relationships: Data integrity and referential constraints
Database Migration Strategy: Version control and deployment approach

API Design

Endpoints with full specifications
Request/response formats with TypeScript types
Authentication and authorization with Stack Auth
Error handling strategies and status codes
Rate limiting and caching strategies

Frontend Architecture

Component Hierarchy Documentation

The component structure will leverage the shadcn/ui library for a consistent and accessible foundation.

Layout Structure:

Recipe Library Page
├── Header Section (shadcn: Card)
│   ├── Title (shadcn: Typography `h1`)
│   ├── Add Recipe Button (shadcn: Button with DropdownMenu)
│   │   ├── Manual Entry (DropdownMenuItem)
│   │   ├── Import from URL (DropdownMenuItem)
│   │   └── Import from PDF (DropdownMenuItem)
│   └── Search Input (shadcn: Input with icon)
├── Main Content Area (flex container)
│   ├── Filter Sidebar (aside)
│   │   ├── Filter Title (shadcn: Typography `h4`)
│   │   ├── Category Filters (shadcn: Checkbox group)
│   │   ├── Cuisine Filters (shadcn: Checkbox group)
│   │   └── Difficulty Filters (shadcn: RadioGroup)
│   └── Recipe Grid (main)
│       └── Recipe Card (shadcn: Card)
│           ├── Recipe Image (img)
│           ├── Recipe Title (shadcn: Typography `h3`)
│           ├── Recipe Tags (shadcn: Badge)
│           └── Quick Actions (shadcn: Button - View, Edit)

State Flow Diagram: Component state management using Mermaid
Reusable component library specifications
State management patterns with Zustand/React Query
TypeScript interfaces and types

Security Performance

Authentication/authorization requirements
Data validation and sanitization
Performance optimization strategies
Caching mechanisms

Context Template

Feature PRD: [The content of the Feature PRD markdown file]