-
Notifications
You must be signed in to change notification settings - Fork 1
Troubleshooting
Use this page when installation, skill routing, wiki sync, or validation does not behave as expected.
Checks:
- Confirm the plugin is installed:
claude plugin list. - Start a new Claude Code session; hooks run at session start.
- Confirm the plugin package includes
hooks/session-start.sh. - If installed from a local checkout, confirm the hook is executable.
Codex users should not expect the raw markdown banner. If Codex invokes the package SessionStart hook, the same reminder is returned as JSON under hookSpecificOutput.additionalContext.
Add the marketplace before installing:
claude plugin marketplace add pitimon/8-habit-ai-devFor Codex:
codex plugin marketplace add pitimon/8-habit-ai-devChecks:
- Verify plugin installation with your runtime's plugin list command.
- Start a fresh session.
- Invoke a known skill directly, such as
/workflowor/requirements. - For Codex, confirm
AGENTS.mdandskills/RESOLVER.mdare available to the runtime.
There are no local changes for the skill to inspect. Run it after generating or editing code, or pass the relevant diff or PR context.
Ask for alternatives explicitly: "Show at least two viable options with trade-offs and a recommendation." Architecture decisions should not be hidden inside a single path.
Ask it to split the task until each item is independently reviewable and has a clear validation step.
Use /operational-state before closing it. Recovered is not always fixed; the skill helps distinguish self-resolved, false positive, accepted known issue, handoff, and active incident states.
Use /consistency-check incident/config mode. It checks symptom, evidence, root cause, actual fix, deploy path, and live verification without requiring persisted PRD/design/task artifacts.
Use /deploy-guide reconciliation gates. Compare planned target, provider-selected target, desired/min/max capacity, readiness, scheduling state, and follow-up action before calling the rollout complete.
The wiki is generated from docs/wiki/. Edit the repository file and open a PR instead of editing the GitHub Wiki web UI directly.
Confirm the repository wiki is enabled and the sync workflow has permission to push to the wiki repository. Then inspect the failing action log.
Check the link-check workflow output. Fix broken external URLs or update the allowlist only for known flaky URLs.
Run local validation from the repository root:
git diff --check
bash tests/validate-structure.sh
bash tests/validate-content.shIf a validator fails, read the first failure carefully; later failures often cascade.
Source of truth: this wiki is generated from docs/wiki/. Edits made through the GitHub Wiki web UI may be overwritten by the next sync. To change a page, open a PR against the repository source file.
Repository · Issues · README · License
Workflow discipline for AI-assisted development
Start
Workflow
- Overview
- 0 · Research
- 1 · Requirements
- 2 · Design
- 3 · Breakdown
- 4 · Build Brief
- 5 · Review AI
- 6 · Deploy Guide
- 7 · Monitor Setup
Operations
Reference
- Habits Reference
- Maturity Model
- Whole Person Assessment
- Architecture
- Glossary
- Limitations
- Vibe Coding vs Structured
- Harness Engineering
Project