create-agentic-pdlc 1.2.1 → 2.0.0

package/templates/.github/workflows/upstream-gate.yml

@@ -0,0 +1,54 @@
+name: Upstream Gate 1
+
+on:
+  issue_comment:
+    types: [created]
+
+jobs:
+  evaluate-gate:
+    name: Evaluate Brainstorming Approval
+    if: ${{ !github.event.issue.pull_request && contains(github.event.issue.labels.*.name, 'upstream:brainstorming') }}
+    runs-on: ubuntu-latest
+    env:
+      PROJECT_TOKEN: ${{ secrets.PROJECT_TOKEN }}
+    steps:
+      - name: Check for approval and swap label
+        if: ${{ env.PROJECT_TOKEN != '' }}
+        uses: actions/github-script@v7
+        with:
+          github-token: ${{ env.PROJECT_TOKEN }}
+          script: |
+            const comment = context.payload.comment.body.toLowerCase();
+            const isApproved = 
+              comment.includes('approved') || 
+              comment.includes('lgtm') || 
+              /option\s+[a-z0-9]/i.test(comment) ||
+              /go\s+with\s+[a-z0-9]/i.test(comment) ||
+              /proceed/i.test(comment);
+
+            if (isApproved) {
+              const { owner, repo } = context.repo;
+              const issue_number = context.payload.issue.number;
+
+              console.log('Approval detected, swapping labels...');
+
+              try {
+                await github.rest.issues.removeLabel({
+                  owner,
+                  repo,
+                  issue_number,
+                  name: 'upstream:brainstorming'
+                });
+              } catch (e) {
+                console.log('Could not remove upstream:brainstorming label');
+              }
+
+              await github.rest.issues.addLabels({
+                owner,
+                repo,
+                issue_number,
+                labels: ['upstream:detailing']
+              });
+            } else {
+              console.log('No approval pattern detected in the comment.');
+            }

package/templates/AGENTS.md

@@ -35,7 +35,33 @@ Always start from the current `main` HEAD. Never work over stale snapshots.
 3. Read all files mentioned in the issue's technical context.
 4. Implement the **minimum viable change** that satisfies the ACs — do not refactor beyond scope.
 5. Run tests: `{{TEST_COMMAND}}`
-6. Create a Pull Request with `Closes #N` in the body — automation moves the board.
+6. Run typecheck (if applicable): `{{TYPECHECK_COMMAND}}`
+7. Create a Pull Request with `Closes #N` in the body — automation moves the board.
+
+### Spec format (Upstream Agents)
+
+When detailing a solution in an issue body, you must **always** include both the user story and the acceptance criteria. Never append only the ACs to an existing text; rewrite the full issue body in this standard format:
+
+```
+**As** [user],
+**I want** [action],
+**so that** [benefit].
+
+---
+
+## Acceptance Criteria
+
+**AC1 — ...**
+- Given ...
+- When ...
+- Then ...
+
+**AC2 — ...**
+...
+
+## Files to modify
+- `path/to/file.ts` — what changes
+```
 
 ## What NOT to do
 
@@ -49,5 +75,6 @@ Always start from the current `main` HEAD. Never work over stale snapshots.
 
 - **Tests:** `{{TEST_COMMAND}}`
 - **Lint/Types:** `{{LINT_COMMAND}}`
+- **Typecheck:** `{{TYPECHECK_COMMAND}}`
 - **Build:** `{{BUILD_COMMAND}}`
 {{EXTRA_PATTERNS}}

package/templates/docs/pdlc.md

@@ -72,7 +72,7 @@ REPO         = {{REPO_OWNER}}/{{REPO_NAME}}
 | `stage:detailing` | Issue | Blue | Technical spec is being written |
 | `stage:development` | Issue | Orange | Agent is implementing the spec |
 | `spec:approved` | Issue | Green | Gate 2 — agent is cleared to implement |
-| `pr:review` | PR | Yellow | Awaiting code review |
+| `pr:in-review` | PR | Yellow | Awaiting code review |
 | `pr:approved` | PR | Green | Code review approved |
 
 ## Approval Gates