Add 5 pi extensions: pi-subagents, pi-crew, rpiv-pi, pi-interactive-shell, pi-intercom

This commit is contained in:
2026-05-08 15:59:25 +10:00
parent d0d1d9b045
commit 31b4110c87
457 changed files with 85157 additions and 0 deletions

View File

@@ -0,0 +1,50 @@
```markdown
---
date: {YYYY-MM-DD}
author: {User from injected git context}
commit: {commit-hash}
branch: {Current branch name}
repository: {Repository name}
topic: "{Feature Name}"
tags: [test-cases, outline, {module}, {feature-slug}]
status: pending | partial | generated
feature: "{Feature Name}"
module: {MOD}
portal: {Portal Name}
slug: {feature-slug}
tc_count: 0
last_updated: {YYYY-MM-DD}
last_updated_by: {User from injected git context}
---
## Routes
- `{route path}` — {ComponentName}
## Endpoints
- `{HTTP method} {path}` — {description}
## Scope Decisions
- {What's in scope and why}
- {What's OUT of scope and why}
## Domain Context
- {Business rules, intentional behaviors, known limitations}
## Test Data Requirements
- {Minimum data conditions for testing this feature}
## Checkpoint History
### {YYYY-MM-DD}
**Q: {Question asked during checkpoint}**
A: {Developer's answer}
```
**Notes on `_meta.md` content:**
- Routes come from route discovery findings — path and component name only, no file:line
- Endpoints come from backend discovery, filtered to those serving this feature
- Scope Decisions, Domain Context, and Test Data Requirements come from checkpoint answers
- Checkpoint History records dated Q&A pairs from developer checkpoints
- If a feature has no frontend routes (e.g., widget), list the component entry point instead
- If status is "partial", add an `## Existing Test Cases` section listing TC IDs found by the test-case-locator agent
- commit records which commit was analyzed during outline generation — used for staleness detection by consuming skills
- tc_count starts at 0 and is updated by write-test-cases when TCs are created

View File

@@ -0,0 +1,36 @@
```markdown
# {Project Name} — Test Case Outline
## Overview
- Project: {project name}
- Framework: {framework}
- Applications: {N} ({app names})
- Total features: {N} outlined
- Backend endpoints: ~{N} across {M} controllers
- Last updated: {YYYY-MM-DD} | Branch: `{branch}` | Commit: `{commit}`
## Features by Portal
### {Portal Name} ({N} features)
| # | Feature | Module | Slug | Routes | Endpoints | Status |
|---|---------|--------|------|--------|-----------|--------|
| 1 | {name} | {MOD} | {slug} | {N} | {M} | pending |
## Backend-Only Endpoints (no frontend exposure)
- **{Group name}** ({N} controllers, ~{M} endpoints) — {reason}
## Next Steps
Generate test cases for a specific feature:
```
/skill:write-test-cases {feature-name}
```
To update this outline after codebase changes:
```
/skill:outline-test-cases
```
Incremental runs detect existing outlines and take faster paths.
## Coverage
This outline was generated by static code analysis. It may not capture dynamically loaded features, features behind feature flags, or functionality added after the generation date. Re-run `outline-test-cases` periodically or add features manually.
```