template-instructions 1.0.1 → 1.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +40 -6
- package/bin/cli.js +1 -1
- package/instructions/global.md +8 -2
- package/instructions/usage.md +1 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -44,20 +44,54 @@ Instead of one "generic" AI trying to do everything, you get specialized experts
|
|
|
44
44
|
- Optimized for iterative development.
|
|
45
45
|
- Keeps files organized by Sprint (`docs/sprints/sprint-X/`), preventing clutter and ensuring version control.
|
|
46
46
|
|
|
47
|
+
## � Installation
|
|
48
|
+
|
|
49
|
+
### Prerequisites
|
|
50
|
+
- Node.js (version 14 or higher)
|
|
51
|
+
- npm or yarn
|
|
52
|
+
|
|
53
|
+
### Install the CLI Tool
|
|
54
|
+
```bash
|
|
55
|
+
npm install -g template-instructions
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
### Create a New Project with Instructions
|
|
59
|
+
```bash
|
|
60
|
+
create-instructions my-sdlc-project
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
This will create a new folder `my-sdlc-project` containing all the instruction files and templates.
|
|
64
|
+
|
|
65
|
+
### Manual Setup
|
|
66
|
+
Alternatively, clone this repository and copy the `instructions/` folder to your desired location.
|
|
67
|
+
|
|
68
|
+
## 🔧 Setup with Gemini
|
|
69
|
+
|
|
70
|
+
1. Copy the instruction files to your Gemini workspace:
|
|
71
|
+
```bash
|
|
72
|
+
cp -r instructions/ ~/.gemini/instructions/
|
|
73
|
+
```
|
|
74
|
+
(Or manually copy the `instructions/` folder to `.gemini/instructions/` in your project.)
|
|
75
|
+
|
|
76
|
+
2. Ensure your Gemini configuration points to this instructions directory.
|
|
77
|
+
|
|
47
78
|
## 📁 Repository Structure
|
|
48
79
|
|
|
49
80
|
```
|
|
50
81
|
.
|
|
82
|
+
├── bin/
|
|
83
|
+
│ └── cli.js # CLI tool for scaffolding new projects
|
|
51
84
|
├── instructions/
|
|
52
|
-
│ ├── global.md
|
|
53
|
-
│ ├── usage.md
|
|
54
|
-
│ ├── roles/
|
|
55
|
-
│ │ ├── pm.md, po.md, sa.md...
|
|
56
|
-
│ └── templates/
|
|
85
|
+
│ ├── global.md # Mandatory global rules and SDLC workflows
|
|
86
|
+
│ ├── usage.md # Detailed usage guide and examples
|
|
87
|
+
│ ├── roles/ # Role-specific instruction definitions
|
|
88
|
+
│ │ ├── pm.md, po.md, sa.md... # (PM, PO, SA, UIUX, QA, etc.)
|
|
89
|
+
│ └── templates/ # Standardized document templates
|
|
57
90
|
│ ├── Project-Plan-Template.md
|
|
58
91
|
│ ├── Product-Backlog-Template.md
|
|
59
92
|
│ └── ...
|
|
60
|
-
|
|
93
|
+
├── package.json # Project metadata and scripts
|
|
94
|
+
└── README.md # This file
|
|
61
95
|
```
|
|
62
96
|
|
|
63
97
|
## 🚀 Quick Start
|
package/bin/cli.js
CHANGED
|
@@ -7,7 +7,7 @@ import { fileURLToPath } from 'url';
|
|
|
7
7
|
const __dirname = path.dirname(fileURLToPath(import.meta.url));
|
|
8
8
|
const projectName = process.argv[2] || 'my-new-project';
|
|
9
9
|
const targetPath = path.join(process.cwd(), projectName);
|
|
10
|
-
const templatePath = path.join(__dirname, '
|
|
10
|
+
const templatePath = path.join(__dirname, '../instructions'); // Folder containing your template files
|
|
11
11
|
|
|
12
12
|
async function scaffold() {
|
|
13
13
|
try {
|
package/instructions/global.md
CHANGED
|
@@ -194,8 +194,14 @@ Handled by REPORTER or STAKEHOLDER when:
|
|
|
194
194
|
- Use screenshots, recordings, or browser artifacts for proof
|
|
195
195
|
- All agents must produce verifiable artifacts (logs, reports, diagrams)
|
|
196
196
|
|
|
197
|
-
###
|
|
198
|
-
|
|
197
|
+
### 10. Mandatory Reporting
|
|
198
|
+
After completing any task or phase, the role **MUST** create the corresponding report file as specified in the Artifact Naming Convention. This ensures full traceability and audit trail.
|
|
199
|
+
|
|
200
|
+
- **No task is considered complete without its artifact.**
|
|
201
|
+
- Artifacts must be placed in the exact folder structure: `docs/sprints/sprint-[N]/[category]/`
|
|
202
|
+
- Use version numbers (v1, v2, etc.) for revisions.
|
|
203
|
+
|
|
204
|
+
### 11. Completion Criteria
|
|
199
205
|
- ✅ STAKEHOLDER approves
|
|
200
206
|
- ✅ No critical/high bugs remain
|
|
201
207
|
- ✅ All Must-Have features delivered and verified
|
package/instructions/usage.md
CHANGED
|
@@ -178,6 +178,7 @@ Artifacts are organized by type in the `docs/` folder:
|
|
|
178
178
|
- Provide clear approval before phase transitions
|
|
179
179
|
- Use correct tags to invoke roles
|
|
180
180
|
- Review generated artifacts
|
|
181
|
+
- **Create and save the required report file after completing any task**
|
|
181
182
|
|
|
182
183
|
### ❌ DON'T:
|
|
183
184
|
- Skip phases (e.g., coding before design approval)
|