Add an issue template for wrapping GMT modules

.github/ISSUE_TEMPLATE/2-feature_request.yaml

@@ -1,4 +1,4 @@
-name: Feature request - General feature
+name: Feature request
 description: Request the addition of a new feature/functionality
 labels: ["feature request"]
 body:

.github/ISSUE_TEMPLATE/3-module_request.md

@@ -0,0 +1,39 @@
+---
+name: Wrapper for a GMT module
+about: Track the progress of wrapping a GMT module. [For project maintainers only!]
+title: "Wrapper: Description of the module"
+labels: ["feature request"]
+
+---
+
+*This issue serves as the central place for discussing and tracking the implementation of the `<wrapper>` method in PyGMT. The issue will be closed when the initial implementation is complete. Progress is tracked at https://github.com/orgs/GenericMappingTools/projects/3.*
+
+## Documentation
+
+- GMT: https://docs.generic-mapping-tools.org/dev/<module>.html
+- GMT.jl: https://www.generic-mapping-tools.org/GMTjl_doc/documentation/modules/<module>
+- PyGMT: https://www.pygmt.org/dev/api/generated/<wrapper>.html
+
+## GMT Option Flags and Modifieres
+
+☑️: *Implemented*; ⬜: *To be implemented/discussed*; ~~Strikethrough~~: *Won't implement*.
+
+- [ ] `-R`: `region` #XXX @XXX
+- [ ] `-J`: `projection` #XXX @XXX
+- [ ] ...
+- [ ] ~~`-U`~~: Use `Figure.timestamp` instead.
+- [ ] ~~`-X`/`-Y`~~: Use `Figure.shift_origin` instead.
+- [ ] ~~`--PAR=value`~~: Use `pygmt.config` instead.
+
+## Notes on Input Formats
+
+*Add any notes on the input formats, especially the meaning of columns.*
+
+## Linked Pull Requests
+
+- [ ] Initial feature implementation #XXX @XXX
+- [ ] Add a tutorial or gallery example
+
+## Related Issues and Discussions
+
+*Add links to related wrapper discussions, API design threads, or upstream GMT changes here.*