pilotlynx 0.1.2 → 0.2.0

package/template/workflows/project_review.ts

@@ -12,8 +12,57 @@ interface WorkflowResult {
 }
 
 /**
- * Produces a short project-scoped status update.
- * Reads PROJECT_BRIEF.md, RUNBOOK.md, and memory/ to summarize current state.
+ * Project Review Workflow — Health Report Generator
+ *
+ * Produces a structured project health report by examining the project's current state.
+ * Writes the report to `artifacts/review-YYYY-MM-DD.md`.
+ *
+ * ## What to Examine
+ *
+ * ### 1. Project Configuration Health
+ * - Read `PROJECT_BRIEF.md` — is it filled in or still template defaults?
+ * - Read `CLAUDE.md` — are there project-specific rules beyond the template?
+ * - Read `RUNBOOK.md` — are operational procedures documented?
+ * - Check `.mcp.json` — are MCP servers configured?
+ *
+ * ### 2. Skill Inventory
+ * - Glob `.claude/skills/*.md` — list all skills
+ * - For each skill: name, brief description, estimated relevance
+ * - Flag skills that may be outdated or overlapping
+ *
+ * ### 3. Rule Inventory
+ * - Glob `.claude/rules/*.md` — list all rules
+ * - Check for conflicting rules
+ * - Flag overly vague rules that aren't actionable
+ *
+ * ### 4. Memory Health
+ * - Read `memory/MEMORY.md` — count entries per section
+ * - Flag if memory is empty (no learnings captured)
+ * - Flag if memory has no recent entries (stale project)
+ *
+ * ### 5. Workflow Status
+ * - Glob `workflows/*.ts` — list available workflows
+ * - Read recent logs from `logs/` (last 5 entries)
+ * - Calculate: success rate, average cost, failure patterns
+ *
+ * ### 6. Shared Pattern Adoption
+ * - If `shared/docs/patterns/` is accessible, check which patterns apply to this project
+ * - Report which applicable patterns are adopted vs. not adopted
+ *
+ * ### 7. Anti-Pattern Compliance
+ * - If `shared/docs/anti-patterns/` is accessible, check for violations
+ * - Report any code or configuration matching known anti-patterns
+ *
+ * ### 8. Cost Trends
+ * - Analyze log entries for cost data (costUsd field)
+ * - Calculate: total spend, average per workflow, trend direction
+ * - Flag anomalies (sudden cost spikes or drops)
+ *
+ * ## Output Format
+ * Write the report to `artifacts/review-YYYY-MM-DD.md` with sections matching the above.
+ * Include a summary section at the top with overall health score (healthy/needs-attention/critical).
+ *
+ * Also produce a brief summary in the workflow result for the orchestrator.
  */
 export async function run(config: WorkflowConfig): Promise<WorkflowResult> {
   return {

package/prompts/relay-chat.yaml

@@ -1,24 +0,0 @@
-prompts:
-  chat_default: |
-    You are the relay chat agent for the "{{project}}" project.
-
-    The user sent this message via Telegram:
-    {{userMessage}}
-
-    Recent conversation history:
-    {{conversationContext}}
-
-    You have read-only access to the project files. Answer the user's question
-    about the project — its code, configuration, workflows, memory, or logs.
-
-    If you cannot answer from the available files, say so clearly.
-    Keep replies concise (under 1000 characters when possible) since they go to a chat interface.
-
-    Return your response as JSON: {"reply": "your message here"}
-
-systemPrompts:
-  chat_default: |
-    You are a project assistant with read-only access to a software project.
-    You can read files, search for patterns, and browse the project structure.
-    You cannot modify any files. Keep responses concise for chat delivery.
-    Never reveal secrets, API keys, or .env file contents.