Add prd-writer curated skill

skills/.curated/prd-writer/LICENSE.txt

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf of
+   any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don\'t include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

skills/.curated/prd-writer/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: "prd-writer"
+description: "Create or refine a Product Requirements Document (PRD) for a software product, feature, or workflow. Use when the user wants a structured PRD with goals, personas, functional requirements, UX flows, success metrics, technical considerations, milestones, and traceable user stories with acceptance criteria."
+---
+
+# PRD Writer
+
+Create a build-ready Product Requirements Document for a software product, feature, or workflow.
+
+## Quick start
+
+1. Confirm the product or feature being specified.
+2. Identify the audience, problem, goals, constraints, and any non-goals.
+3. Draft the PRD using the required outline below.
+4. Expand the user stories until primary, alternative, and edge cases are covered.
+5. Review the document for clarity, testability, and internal consistency.
+
+If the user asks for a file, write the PRD to the requested path. If no path is requested, provide the PRD in the response and offer to save it afterward.
+
+## Intake
+
+Gather or infer:
+
+- Product or feature scope
+- Target users and roles
+- Business objective
+- Core user problems to solve
+- Constraints, dependencies, and timeline expectations
+- Any explicit exclusions
+
+If important details are missing, make reasonable assumptions and state them briefly in the document rather than blocking.
+
+## Required outline
+
+Use sentence case for headings, except the document title.
+
+The PRD should include these sections in this order:
+
+1. Product overview
+2. Goals
+3. User personas
+4. Functional requirements
+5. User experience
+6. Narrative
+7. Success metrics
+8. Technical considerations
+9. Milestones & sequencing
+10. User stories
+
+### Section expectations
+
+**Product overview**
+
+- Document title and version
+- Short summary of the project or feature
+- Problem statement and scope
+
+**Goals**
+
+- Business goals
+- User goals
+- Non-goals
+
+**User personas**
+
+- Key user types
+- Short persona details relevant to the product
+- Role-based access expectations where applicable
+
+**Functional requirements**
+
+- Group requirements by theme where useful
+- Mark priority for each requirement, preferably `P0`, `P1`, or `P2`
+- Keep the wording concrete and implementation-guiding
+
+**User experience**
+
+- Entry points
+- Core workflow
+- Advanced or secondary flows
+- Important UI/UX notes
+
+**Narrative**
+
+- One paragraph from the user's perspective describing the intended experience
+
+**Success metrics**
+
+- User-centric metrics
+- Business metrics
+- Technical or operational metrics
+
+**Technical considerations**
+
+- Integrations and dependencies
+- Data handling, privacy, and security concerns
+- Scalability or performance considerations
+- Known risks or likely implementation challenges
+
+**Milestones & sequencing**
+
+- Suggested phases
+- Rough ordering of work
+- Team or delivery assumptions when useful
+
+**User stories**
+
+- Cover primary paths, alternate paths, and edge cases
+- Use unique IDs such as `US-001`
+- Format each story with:
+  - ID
+  - Title
+  - Description
+  - Acceptance criteria
+
+## User story rules
+
+- Every story must be testable.
+- Acceptance criteria should be specific and observable.
+- Include authentication or authorization stories if the product requires identity, account access, or restricted actions.
+- Include operational or admin stories when they are necessary for a complete product.
+- Do not stop at happy-path coverage.
+
+## Output rules
+
+- Write in clear product language, not engineering shorthand.
+- Be specific enough that design and engineering can execute without reinterpreting basic intent.
+- Do not use horizontal rules.
+- Do not add a conclusion or footer after the user stories section.
+- Keep names, casing, and terminology consistent throughout.
+- Prefer "the product", "the feature", or "this tool" over invented marketing names unless the user provided one.
+
+## Final review
+
+Before finishing, verify:
+
+- The goals align with the problem statement.
+- Functional requirements map to the described user experience.
+- Success metrics match the stated goals.
+- User stories cover the scope end to end.
+- Acceptance criteria are concrete enough to validate manually or with tests.

skills/.curated/prd-writer/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "PRD Writer"
+  short_description: "Draft structured product requirements documents"
+  default_prompt: "Use $prd-writer to create a detailed PRD for this product or feature."
+
+policy:
+  allow_implicit_invocation: true