Communitygithub.com

cdcoonce/Portfolio_Website

透過使用者訪談、程式碼探索和模組設計建立產品需求文件 (PRD),並以 GitHub 議題形式提交。當使用者想撰寫 PRD、建立產品需求文件或規劃新功能時使用。

Portfolio_Website 是什麼?

這項技能旨在引導 AI 代理 (如 Claude Code) 建立高品質的產品需求文件 (PRD)。它會先要求使用者詳細描述問題,並探索相關程式碼庫以驗證其假設。接著,技能會引導代理進行深入的、逐層遞進的「使用者訪談」,以釐清需求並解決決策依賴關係。最後,它會協助推導出主要模組,並使用一個結構化的範本產出完整的 PRD,最終以 GitHub 議題的形式提交。此流程特別強調產出「深度模組」,這些模組能將複雜功能封裝在簡單、可測試且不易變更的介面中,從而提升程式碼品質與可維護性。其目標是建立一份能作為可靠開發藍圖、涵蓋問題、解決方案、使用者故事、實作與測試決策的全面文件,適用於任何需要系統化規劃新功能的開發情境。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/cdcoonce/Portfolio_Website/tree/HEAD/.claude/skills/write-a-prd

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

當使用者想要建立 PRD 時,將會呼叫此技能。如果你認為某些步驟不必要,可以跳過它們。

  1. 向使用者詢問他們想要解決的問題的詳細描述,以及任何潛在的解決方案想法。

  2. 探索儲存庫以驗證他們的論點,並了解程式碼庫的當前狀態。

  3. 對使用者進行有關此計畫各個方面的徹底訪談,直到達成共同的理解。逐步探索設計樹的每個分支,逐一解決決策之間的依賴關係。

  4. 勾勒出你需要建置或修改以完成實作的主要模組。積極尋找機會來提取可以獨立測試的深度模組。

深度模組 (相對於淺層模組) 是一種將大量功能封裝在簡單、可測試且鮮少變更的介面中的模組。

與使用者確認這些模組是否符合他們的期望。並與使用者確認他們希望為哪些模組撰寫測試。

  1. 一旦你對問題和解決方案有了完整的理解,請使用下面的範本撰寫 PRD。PRD 應以 GitHub 議題的形式提交。

問題陳述

從使用者的角度來看,使用者面臨的問題。

解決方案

從使用者的角度來看,問題的解決方案。

使用者故事

一個詳盡的、編號的使用者故事列表。每個使用者故事應採用以下格式:

  1. 身為 <角色>,我想要 <功能>,以便 <利益>

這份使用者故事列表應極其詳盡,並涵蓋該功能的所有面向。

實作決策

一個已做出的實作決策列表。這可以包含:

  • 將會建置/修改的模組
  • 將會修改的模組介面
  • 來自開發者的技術說明
  • 架構決策
  • 綱要變更
  • API 合約
  • 特定的互動

請勿包含特定的檔案路徑或程式碼片段。它們可能很快就會過時。

測試決策

一個已做出的測試決策列表。包含:

  • 良好測試的定義描述 (僅測試外部行為,而非實作細節)
  • 哪些模組將會被測試
  • 測試的既有範例 (即程式碼庫中類似類型的測試)

不在此限

本 PRD 範圍內不包含的事項描述。

其他備註

關於該功能的任何其他備註。

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

cdcoonce/Portfolio_Website

Git commit workflow with enforced conventional commit style. Use when Claude needs to stage and commit changes, craft commit messages, or the user asks to commit, make a commit, or save their work. Ensures consistent commit message format, proper scoping, and atomic commits across the project.

cdcoonce/Portfolio_Website

AI-powered code quality analysis for Python, Markdown, and Mermaid diagrams. Use this skill when: (1) reviewing code for quality issues, (2) checking Python files for PEP8 violations, unused code, missing type hints, docstring problems, complexity issues, or potential runtime errors, (3) validating Markdown documentation for broken links, heading structure, or formatting issues, (4) validating Mermaid diagram syntax, (5) the user asks for a "code review" or "quality check", (6) analyzing code snippets pasted in conversation, or (7) suggesting and applying fixes for code quality issues.

cdcoonce/Portfolio_Website

Deploy the portfolio chat agent Lambda function to AWS. Use when the user asks to deploy, redeploy, push to Lambda, update the chat agent, or after updating context files or lambda_function.py. Rebuilds the knowledge base, packages dependencies, and deploys to AWS Lambda.

cdcoonce/Portfolio_Website

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

cdcoonce/Portfolio_Website

Orchestrate the full GitHub-issues-driven development lifecycle. 7-phase pipeline from brainstorm through PR with state tracking and cross-conversation resume. Use when user says "dev cycle", "development workflow", "full development pipeline", or invokes /dev-cycle.

cdcoonce/Portfolio_Website

Production Python coding standards with automatic version detection (3.10-3.13). Use when writing, reviewing, or refactoring Python to ensure adherence to modern type syntax, LBYL exception handling, pathlib operations, ABC-based interfaces, and production-tested patterns. Not Dagster-specific - applies to any Python project.

cdcoonce/Portfolio_Website

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

cdcoonce/Portfolio_Website

GitHub CLI (gh) integration for managing issues, pull requests, branches,

cdcoonce/Portfolio_Website

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

cdcoonce/Portfolio_Website

Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.

cdcoonce/Portfolio_Website

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when the user asks for a plan review, CEO review, mega review, or wants a plan challenged/stress-tested before implementation.

cdcoonce/Portfolio_Website

Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.

cdcoonce/Portfolio_Website

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in docs/plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

cdcoonce/Portfolio_Website

Generate or update the `.claude/docs/project.md` file that gives Claude project-specific context. Use this skill when the user asks to create, update, regenerate, or refresh project context, or says things like "update project.md", "generate project context", "this repo needs a project.md", or "Claude doesn't know about this project". Also trigger when onboarding Claude to a new repository for the first time.

cdcoonce/Portfolio_Website

Generate comprehensive, high-quality README.md files for code repositories. Use this skill whenever the user asks to create, write, generate, update, or improve a README for any project or repository. Also trigger when the user says things like "document this project", "write docs for this repo", "this repo needs a README", "help me onboard developers to this codebase", or asks for project documentation in markdown. Even if the user just says "README" or "readme" in the context of a codebase, use this skill.

cdcoonce/Portfolio_Website

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

cdcoonce/Portfolio_Website

Set up pre-commit hooks for the current repo. Use when user wants to add pre-commit hooks, configure commit-time linting, formatting, type checking, or testing. Triggers on "pre-commit", "git hooks", "linting hooks", or /setup-pre-commit.

cdcoonce/Portfolio_Website

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

cdcoonce/Portfolio_Website

Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.

cdcoonce/Portfolio_Website

Rewrites the prose sections of wiki pages in-place. Reads source files to understand current context, then updates only the content inside <!-- claude:prose --> ... <!-- claude:prose:end --> markers. Never touches <!-- generated:start --> ... <!-- generated:end --> blocks. Supports targeting a single page with /update-wiki {PageName}.

相關技能