pi-feature-dev 1.8.0 → 1.9.1

package/README.md

@@ -19,6 +19,9 @@ isolated workers, Git task commits, internal reviews, finalize, and a portable
 run summary. It is portable across host agents that provide fresh-context
 isolated workers and Git access.
 
+The `final-check` skill asks: “What else have we missed? Is there anything we
+need to check or fix?”
+
 The `grill` skill runs a dependency-aware interview that researches facts,
 exhausts the current decision frontier round by round, sharpens domain language,
 and records agreed terminology and durable architectural decisions.
@@ -98,6 +101,12 @@ Run a plan with `plan-exec`:
 /skill:plan-exec docs/plans/20260518-example.md
 ```
 
+Run a final completeness check on the current work:
+
+```text
+/skill:final-check
+```
+
 Stress-test an idea before planning or implementation:
 
 ```text
@@ -154,6 +163,9 @@ pi-feature-dev/
     ├── feature-dev/
     │   ├── agents/openai.yaml
     │   └── SKILL.md
+    ├── final-check/
+    │   ├── agents/openai.yaml
+    │   └── SKILL.md
     ├── grill/
     │   ├── agents/openai.yaml
     │   ├── SKILL.md

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-feature-dev",
-  "version": "1.8.0",
+  "version": "1.9.1",
   "description": "Portable coding-agent workflows packaged as skills.",
   "license": "MIT",
   "type": "module",

package/skills/final-check/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: final-check
+description: What else have we missed? Is there anything we need to check or fix? Use when the user invokes `$final-check`.
+---
+
+What else have we missed? Is there anything we need to check or fix?

package/skills/final-check/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "What Did We Miss?"
+  short_description: "What else should we check or fix?"
+  default_prompt: "$final-check: What else have we missed? Is there anything we need to check or fix?"

package/skills/grill/SKILL.md

@@ -18,6 +18,10 @@ Do not implement the resulting plan or design during or immediately after the gr
 
 Never turn a discoverable fact into homework for the user. Never silently turn an unresolved decision into an assumption.
 
+## Resolve bundled resources
+
+Before invoking a read for any relative reference in this skill, resolve it against the directory containing the selected `grill/SKILL.md`. Use that resolved path for the read. Never use the global skills directory, the current working directory, or the repository root as the base.
+
 ## Workflow
 
 ### 1. Establish the subject
@@ -86,7 +90,7 @@ Continue until no unresolved branch can materially affect the result. Respect an
 
 ## Record decisions during the grill
 
-When a project term is explicitly resolved, update the applicable `CONTEXT.md` immediately. Read and follow [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md) before the first update. Keep `CONTEXT.md` a glossary only: no implementation details, requirements, scratch notes, or architectural decisions.
+When a project term is explicitly resolved, update the applicable `CONTEXT.md` immediately. Resolve [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md) from the selected `grill/SKILL.md` directory, then read and follow it before the first update. Keep `CONTEXT.md` a glossary only: no implementation details, requirements, scratch notes, or architectural decisions.
 
 Offer an ADR only when all three conditions hold:
 
@@ -94,7 +98,7 @@ Offer an ADR only when all three conditions hold:
 2. The choice would be surprising without its context.
 3. Genuine alternatives were considered and rejected for specific reasons.
 
-If any condition is missing, do not create an ADR. If all three hold, ask the user whether to record it, then read and follow [ADR-FORMAT.md](./ADR-FORMAT.md). Create directories and files lazily.
+If any condition is missing, do not create an ADR. If all three hold, ask the user whether to record it, then resolve [ADR-FORMAT.md](./ADR-FORMAT.md) from the selected `grill/SKILL.md` directory and read and follow it. Create directories and files lazily.
 
 ## Finish with a confirmed session result