Skip to content

Commit 9fbed2f

Browse files
authored
chore: Create feature_request.md
1 parent 4c2283a commit 9fbed2f

1 file changed

Lines changed: 73 additions & 0 deletions

File tree

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
<!-- .github/ISSUE_TEMPLATE/feature_request.md -->
2+
3+
---
4+
name: ✨ Feature Request
5+
about: Suggest an improvement, new detection, module, integration, or UX enhancement
6+
title: "[FEATURE] "
7+
labels: enhancement
8+
assignees: ''
9+
10+
---
11+
12+
## PyADRecon Feature Request
13+
14+
Please fill out the information below to help us understand the use case and scope of your proposal.
15+
16+
---
17+
18+
### 📌 Summary
19+
20+
**Describe the feature you’re proposing in one or two sentences.**
21+
22+
---
23+
24+
### 🎯 Motivation
25+
26+
- What problem does this solve?
27+
- Who benefits (e.g., blue team, red team, auditors)?
28+
- Are there existing tools or workflows this integrates with or complements?
29+
30+
---
31+
32+
### 💡 Proposed Behavior
33+
34+
Describe how you envision this working:
35+
36+
- New command-line options?
37+
- New report sections?
38+
- New detection logic?
39+
- New modules?
40+
- What inputs/output formats should it use?
41+
42+
---
43+
44+
### 🧪 Example Usage (optional)
45+
46+
If applicable, show example commands and expected output:
47+
48+
```
49+
# e.g., pyadrecon --detect-dmsa
50+
```
51+
52+
```
53+
DelegatedMSAs:
54+
- dMSA: SQL-SvcAcct
55+
Password Readers: Domain Users
56+
Risk Level: CRITICAL
57+
```
58+
59+
---
60+
61+
### 📚 Alternatives Considered
62+
63+
If you considered alternatives (existing tools, different implementations), please describe why this approach is preferred.
64+
65+
---
66+
67+
### 🚀 Additional context
68+
69+
Add any other context about the proposal here.
70+
71+
---
72+
73+
Thank you — your ideas help make PyADRecon better!

0 commit comments

Comments
 (0)