Run any Skill in Manus with one click

deft-directive-product-signal

Stars28

Forks14

UpdatedJuly 23, 2026 at 02:02

Consented agent-driven product check-in (pulse + portrait) with enable and consent gates, minimized local ledger attach, and private GitHub sink submit. Defaults off.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

deftai

deftai/directive

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	deft-directive-product-signal
description	Consented agent-driven product check-in (pulse + portrait) with enable and consent gates, minimized local ledger attach, and private GitHub sink submit. Defaults off.

Deft Directive Product Signal — consented check-in (#2693)

Agent-driven qualitative product-improvement signal for partner/trial installs. Lightweight interview, minimized local summaries (value/health/helped), optional skillsSummary hook — submits to private deftai/product-signal when enable + consent gates pass.

Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.

When to Use

Operator says product check-in, product pulse, partner feedback, or product signal
Partner onboarding after ops enables plan.policy.productSignal
⊗ Do NOT invoke from session:start or ambient rituals when disabled (#2693 D3)

Preconditions

! plan.policy.productSignal.enabled MUST be true (task policy:show --field=productSignal)
! Install-level consent MUST be recorded before outbound submit (task product-signal:status)
! Consent schema v2 binds to the configured sinkRepo; legacy v1 consent authorizes only deftai/product-signal (#2767)
! Re-consent after changing plan.policy.productSignal.sinkRepo; mismatch soft-skips as sink-unconsented
⊗ Prompt or submit when enabled is false
⊗ Block story work on sink errors — fail open (#2693 D16/D18)

Phase 1 — Gate

task product-signal:status
task policy:show -- --field=productSignal

! If disabled: soft-skip with one line; exit skill
! If headless/CI: fail open — no consent/interview prompts (#2693 D16)

Phase 2 — First-time consent (interactive only, D17)

When enabled, interactive, and consent missing/revoked, ask:

May we collect usage metrics and related session signal from this install to improve Directive? This can include a short check-in plus minimized local summaries (value/health and related ledgers). Nothing is sent while this path is off or without your consent.

If you are unsure, please check with your company before saying no — they are a Directive partner and may already expect this signal to be shared.

Reply yes to consent, or no to decline.

yes → task product-signal:consent -- --grant (pass --project-root when using a custom sinkRepo); continue
no → soft-skip; do not badger every turn

Phase 3 — Interview (≤3 answers + optional NPS)

! Ask at most three short questions plus optional NPS (0–10)
~ Target ≤30s human time beyond first-time consent
⊗ Paste secrets, paths, raw logs, or full USER.md into answers

Phase 4 — Assemble + validate + submit

task product-signal:submit -- --surface pulse --dry-run
task product-signal:submit -- --surface pulse --nps 9

! On validation failure: show reason; no partial write
! On sink ACL/network errors: soft-skip with hint; do not fail caller (#2693 D18)
! Report issue URL on success

Private gaps (D19)

! Record bugs/gaps as Gap: comments on the standing pulse thread (enable+consent sufficient)
! Public promote to deftai/directive remains hard-confirm via deft-directive-feedback / task feedback:file

Revoke

task product-signal:consent -- --revoke
# and/or disable: set plan.policy.productSignal.enabled false

Anti-Patterns

⊗ Ambient consent nag when disabled
⊗ Fail-closed headless behavior
⊗ Sticky forever-fail when sink is down
⊗ Auto-file public framework-gap issues from pulses

Exit

deft-directive-product-signal complete — exiting skill.

More from this repository

same repository

deft-directive-review-cycle

deftai/directive

Greptile / bot reviewer response and PR-shepherding workflow. Use when running a review cycle or babysitting a PR to merge-ready -- audit process prerequisites, fetch bot findings, fix all issues in a single batch commit, and exit cleanly when no P0 or P1 issues remain. Supersedes Cursor global babysit on Deft-managed repos (#2261).

2026-07-2628

deft-directive-swarm

deftai/directive

Parallel local agent orchestration. Use when running multiple agents on story-level xBRIEFs simultaneously — to scan active/ for allocatable work, set up isolated worktrees, launch agents with proven prompts, monitor progress, handle stalled review cycles, and close out PRs cleanly.

2026-07-2628

deft-directive-build

deftai/directive

Build a project from scope xBRIEFs following Deft Directive framework standards. Use after deft-directive-setup has generated the project definition, or when the user has story xBRIEFs in xbrief/active/ ready to implement. Handles scaffolding, implementation, testing, and quality checks phase by phase.

2026-07-2328

deft-directive-pre-pr

deftai/directive

Iterative pre-PR quality improvement loop. Use before pushing a branch for PR creation -- after completing implementation but before task check. Cycles through Read-Write-Lint-Diff until a full pass produces zero changes.

2026-07-2328

deft-directive-article-review

deftai/directive

Evaluate an article, paper, or post for lessons that could improve directive. Analyzes two axes: how concepts improve directive's own implementation, and how they improve the projects directive creates. Produces filtered suggestions, iterates with the user, and optionally creates GitHub issues on the directive repo. Use when evaluating an article, paper, post, or URL for directive improvements, or when the user says "analyze this article", "evaluate this article", or "what can we learn from this for directive".

2026-07-2228

deft-directive-debug

deftai/directive

Systematic, evidence-based root-cause investigation. Use when the user asks "why did X break / slow down / regress?", wants to debug a failure, run a forensic investigation, or find the root cause of a bug -- to enter a sustained investigation MODE with a claim ledger, mandatory falsification before any conclusion, a chat answer-embargo until evidence closes, and a deterministic validator gate. Triggers: "debug", "root cause", "investigate", "why did X break", "why is X slow", "systematic debugging", "forensic".

2026-07-2228