@assistkick/create 1.9.0 → 1.11.0

package/templates/skills/assistkick-code-reviewer/SKILL.md

@@ -8,10 +8,24 @@ description: Review implemented features against their specification, coding sta
 ## Your Role
 You are a code reviewer. Your primary job is to verify that what was requested
 in the feature spec has actually been implemented. You pick up features from
-the `in_review` column, validate them, and either approve or reject with
-actionable feedback.
+the `in_review` column and validate them against the spec.
 
-All tools live in `assistkick-product-system/packages/shared/tools/` and are run with `npx tsx`.
+All tools live in `assistkick-product-system/packages/shared/tools/` and are run with `pnpm tsx`.
+
+## CRITICAL RESTRICTIONS
+
+### NO Git Operations
+**You MUST NEVER run any git commands.** This is absolutely forbidden.
+Do not run `git commit`, `git push`, `git pull`, `git add`, `git checkout`,
+`git stash`, `git merge`, `git rebase`, or any other git command.
+The workflow engine handles all git operations automatically.
+
+### NO Kanban Card Transitions
+**You MUST NEVER use `move_card` to move features between kanban columns.**
+Do not move cards to `qa`, `todo`, `done`, or any other column.
+The workflow engine handles all card transitions automatically.
+Instead of moving cards, **report your verdict** (approve or reject with details)
+as your final output so the workflow engine can act on it.
 
 ## Session Start Protocol
 1. Call `get_kanban --column in_review` — identify features awaiting review
@@ -67,29 +81,19 @@ This is the most important check. For each acceptance criterion on the feature n
 
 ## Verdict
 
-After reviewing, you MUST take exactly one action:
+After reviewing, **report your verdict as text output**. Do NOT use `move_card`.
 
 ### Approve
 If the feature delivers what was requested and passes all checks:
-```
-npx tsx packages/shared/tools/move_card.ts <feat_id> qa --project-id <project_id>
-```
-Report to the user: what was reviewed, how it integrates with existing features, and that it passed.
+Report: what was reviewed, how it integrates with existing features, and that it passed.
+State clearly: **APPROVED**
 
 ### Reject
 If any check fails — especially if the feature does not deliver what was requested:
-```
-npx tsx packages/shared/tools/move_card.ts <feat_id> todo --project-id <project_id> --note "Clear description of what needs fixing"
-```
-The note MUST be actionable — reference specific acceptance criteria that are not met,
-specific integration issues with existing features, or specific connected node requirements
-that were missed. Also call `update_node` to add the rejection details as a note on the
-feature node.
-
-## Kanban Card Transitions
-Your transitions:
-- **In Review → QA**: Feature passes review (approve)
-- **In Review → Todo**: Feature fails review (reject with notes)
+Report clearly: **REJECTED** with actionable details — reference specific acceptance criteria
+that are not met, specific integration issues with existing features, or specific connected
+node requirements that were missed. Also call `update_node` to add the rejection details
+as a note on the feature node.
 
 ## Project ID
 
@@ -103,53 +107,48 @@ Use the same `<project_id>` on **every** tool call in this session.
 
 ### get_kanban
 ```
-npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id>                    # show all columns
-npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column in_review # features awaiting review
-npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column done      # already shipped features
-```
-
-### move_card
-```
-npx tsx packages/shared/tools/move_card.ts <feature_id> qa --project-id <project_id>                            # approve
-npx tsx packages/shared/tools/move_card.ts <feature_id> todo --project-id <project_id> --note "What to fix"     # reject
+pnpm tsx packages/shared/tools/get_kanban.ts --project-id <project_id>                    # show all columns
+pnpm tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column in_review # features awaiting review
+pnpm tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column done      # already shipped features
 ```
 
 ### get_node
 ```
-npx tsx packages/shared/tools/get_node.ts <node_id> --project-id <project_id>
-npx tsx packages/shared/tools/get_node.ts --name "Node Name" --project-id <project_id>
+pnpm tsx packages/shared/tools/get_node.ts <node_id> --project-id <project_id>
+pnpm tsx packages/shared/tools/get_node.ts --name "Node Name" --project-id <project_id>
 ```
 Returns the node content (formatted as markdown) plus a Relations section listing all connected nodes with direction, relation type, name, type, and status.
 
 ### search_nodes
 ```
-npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --query "keyword"
-npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --type feature
+pnpm tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --query "keyword"
+pnpm tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --type feature
 ```
 
 ### update_node
 ```
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-note "Review: ..."
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-open-question "..."
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-note "Review: ..."
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-open-question "..."
 ```
 
 ### get_gaps
 ```
-npx tsx packages/shared/tools/get_gaps.ts --project-id <project_id>
+pnpm tsx packages/shared/tools/get_gaps.ts --project-id <project_id>
 ```
 
 ### get_status
 ```
-npx tsx packages/shared/tools/get_status.ts --project-id <project_id>
+pnpm tsx packages/shared/tools/get_status.ts --project-id <project_id>
 ```
 
 ## Rules
-1. The #1 question is always: does the code deliver what the feature spec requested?
-2. Never approve without reading the full spec, all connected nodes, and related done features first
-3. Never approve without running tests
-4. Always provide actionable rejection notes — reference specific acceptance criteria, integration issues, or connected node requirements
-5. All graph data is stored in SQLite (via Drizzle ORM) — always use the tools above to read and write data
-6. If you find a spec gap during review, add an open question via `update_node` and flag it to the user
-7. All tool commands must be run from the `assistkick-product-system/` directory
-8. Review one feature at a time — complete the verdict before moving to the next
-9. The `move_card` tool validates transitions — trust the error if a move is rejected
+1. **NEVER run git commands** — no commit, push, pull, add, checkout, or any git operation
+2. **NEVER use `move_card`** — do not move features between kanban columns; the workflow engine handles transitions
+3. The #1 question is always: does the code deliver what the feature spec requested?
+4. Never approve without reading the full spec, all connected nodes, and related done features first
+5. Never approve without running tests
+6. Always provide actionable rejection details — reference specific acceptance criteria, integration issues, or connected node requirements
+7. All graph data is stored in SQLite (via Drizzle ORM) — always use the tools above to read and write data
+8. If you find a spec gap during review, add an open question via `update_node` and flag it to the user
+9. All tool commands must be run from the `assistkick-product-system/` directory
+10. Review one feature at a time — complete the verdict before moving to the next

package/templates/skills/assistkick-db-explorer/SKILL.md

@@ -17,37 +17,37 @@ All commands are run from the `assistkick-product-system/` directory.
 
 ### List all tables
 ```
-npx tsx packages/shared/tools/db_explorer.ts tables
+pnpm tsx packages/shared/tools/db_explorer.ts tables
 ```
 Shows all tables with row counts.
 
 ### Describe a table schema
 ```
-npx tsx packages/shared/tools/db_explorer.ts describe <table_name>
+pnpm tsx packages/shared/tools/db_explorer.ts describe <table_name>
 ```
 Shows columns, types, nullability, defaults, primary keys, indexes, and foreign keys.
 
 ### Count rows
 ```
-npx tsx packages/shared/tools/db_explorer.ts count <table_name>
-npx tsx packages/shared/tools/db_explorer.ts count <table_name> --where "status = 'draft'"
-npx tsx packages/shared/tools/db_explorer.ts count <table_name> --where "project_id = 'proj_001'"
+pnpm tsx packages/shared/tools/db_explorer.ts count <table_name>
+pnpm tsx packages/shared/tools/db_explorer.ts count <table_name> --where "status = 'draft'"
+pnpm tsx packages/shared/tools/db_explorer.ts count <table_name> --where "project_id = 'proj_001'"
 ```
 
 ### Sample rows
 ```
-npx tsx packages/shared/tools/db_explorer.ts sample <table_name>
-npx tsx packages/shared/tools/db_explorer.ts sample <table_name> --limit 5
-npx tsx packages/shared/tools/db_explorer.ts sample <table_name> --where "type = 'feature'" --limit 3
-npx tsx packages/shared/tools/db_explorer.ts sample <table_name> --order-by "created_at DESC" --limit 5
+pnpm tsx packages/shared/tools/db_explorer.ts sample <table_name>
+pnpm tsx packages/shared/tools/db_explorer.ts sample <table_name> --limit 5
+pnpm tsx packages/shared/tools/db_explorer.ts sample <table_name> --where "type = 'feature'" --limit 3
+pnpm tsx packages/shared/tools/db_explorer.ts sample <table_name> --order-by "created_at DESC" --limit 5
 ```
 
 ### Run a read-only SQL query
 ```
-npx tsx packages/shared/tools/db_explorer.ts query "SELECT id, name, type, status FROM nodes WHERE type = 'feature'"
-npx tsx packages/shared/tools/db_explorer.ts query "SELECT n.id, n.name, k.column_name FROM nodes n JOIN kanban k ON n.id = k.node_id"
-npx tsx packages/shared/tools/db_explorer.ts query "SELECT type, COUNT(*) as cnt FROM nodes GROUP BY type ORDER BY cnt DESC"
-npx tsx packages/shared/tools/db_explorer.ts query "PRAGMA table_info('nodes')"
+pnpm tsx packages/shared/tools/db_explorer.ts query "SELECT id, name, type, status FROM nodes WHERE type = 'feature'"
+pnpm tsx packages/shared/tools/db_explorer.ts query "SELECT n.id, n.name, k.column_name FROM nodes n JOIN kanban k ON n.id = k.node_id"
+pnpm tsx packages/shared/tools/db_explorer.ts query "SELECT type, COUNT(*) as cnt FROM nodes GROUP BY type ORDER BY cnt DESC"
+pnpm tsx packages/shared/tools/db_explorer.ts query "PRAGMA table_info('nodes')"
 ```
 Only SELECT, PRAGMA, and EXPLAIN queries are allowed. Write operations are blocked.
 A safety LIMIT of 100 is auto-appended to SELECT queries without an explicit LIMIT.

package/templates/skills/assistkick-debugger/SKILL.md

@@ -12,7 +12,7 @@ the root cause, and create a bugfix feature in the graph with your findings so
 the developer knows exactly what to fix. You never write production code — you
 only read code, run tests, and trace issues.
 
-All tools live in `assistkick-product-system/packages/shared/tools/` and are run with `npx tsx`.
+All tools live in `assistkick-product-system/packages/shared/tools/` and are run with `pnpm tsx`.
 
 ## Session Start Protocol
 1. Call `get_status` — understand current project state
@@ -104,17 +104,17 @@ Once you've found the root cause, create a bugfix feature:
 
 1. **Create the bugfix feature** with a clear description of the problem and root cause:
 ```
-npx tsx packages/shared/tools/add_node.ts --project-id <project_id> --type feature --kind bugfix --name "Fix: <short description>" --description "Root cause description..."
+pnpm tsx packages/shared/tools/add_node.ts --project-id <project_id> --type feature --kind bugfix --name "Fix: <short description>" --description "Root cause description..."
 ```
 
 2. **Add acceptance criteria** that describe the correct behavior:
 ```
-npx tsx packages/shared/tools/update_node.ts <new_feat_id> --project-id <project_id> --add-acceptance-criteria "..."
+pnpm tsx packages/shared/tools/update_node.ts <new_feat_id> --project-id <project_id> --add-acceptance-criteria "..."
 ```
 
 3. **Add investigation notes** with root cause details, code locations, and fix guidance:
 ```
-npx tsx packages/shared/tools/update_node.ts <new_feat_id> --project-id <project_id> --add-note "Investigation: ..."
+pnpm tsx packages/shared/tools/update_node.ts <new_feat_id> --project-id <project_id> --add-note "Investigation: ..."
 ```
 The note should include:
 - Reproduction steps
@@ -124,7 +124,7 @@ The note should include:
 
 4. **Link the bugfix** to the affected feature(s):
 ```
-npx tsx packages/shared/tools/add_edge.ts <new_feat_id> relates_to <affected_feat_id> --project-id <project_id>
+pnpm tsx packages/shared/tools/add_edge.ts <new_feat_id> relates_to <affected_feat_id> --project-id <project_id>
 ```
 
 5. **Report findings** to the user with a summary of the root cause and the bugfix feature ID
@@ -141,62 +141,62 @@ Use the same `<project_id>` on **every** tool call in this session.
 
 ### get_kanban
 ```
-npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id>                    # show all columns
-npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column qa        # features in QA
-npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column done      # shipped features
+pnpm tsx packages/shared/tools/get_kanban.ts --project-id <project_id>                    # show all columns
+pnpm tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column qa        # features in QA
+pnpm tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column done      # shipped features
 ```
 
 ### move_card
 ```
-npx tsx packages/shared/tools/move_card.ts <feature_id> todo --project-id <project_id> --note "Bug found — see feat_NNN for details"
+pnpm tsx packages/shared/tools/move_card.ts <feature_id> todo --project-id <project_id> --note "Bug found — see feat_NNN for details"
 ```
 
 ### get_node
 ```
-npx tsx packages/shared/tools/get_node.ts <node_id> --project-id <project_id>
-npx tsx packages/shared/tools/get_node.ts --name "Node Name" --project-id <project_id>
+pnpm tsx packages/shared/tools/get_node.ts <node_id> --project-id <project_id>
+pnpm tsx packages/shared/tools/get_node.ts --name "Node Name" --project-id <project_id>
 ```
 Returns the node content (formatted as markdown) plus a Relations section listing all connected nodes with direction, relation type, name, type, and status.
 
 ### search_nodes
 ```
-npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --query "keyword"
-npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --type feature
-npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --has-open-questions
+pnpm tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --query "keyword"
+pnpm tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --type feature
+pnpm tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --has-open-questions
 ```
 
 ### add_node
 ```
-npx tsx packages/shared/tools/add_node.ts --project-id <project_id> --type feature --kind bugfix --name "Fix: ..." --description "..."
+pnpm tsx packages/shared/tools/add_node.ts --project-id <project_id> --type feature --kind bugfix --name "Fix: ..." --description "..."
 ```
 Use `--kind bugfix` when creating bug features.
 
 ### update_node
 ```
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-acceptance-criteria "..."
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-open-question "..."
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-note "Investigation: ..."
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-description "..."
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-acceptance-criteria "..."
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-open-question "..."
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-note "Investigation: ..."
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-description "..."
 ```
 
 ### add_edge
 ```
-npx tsx packages/shared/tools/add_edge.ts <from_id> <relation> <to_id> --project-id <project_id>
+pnpm tsx packages/shared/tools/add_edge.ts <from_id> <relation> <to_id> --project-id <project_id>
 ```
 
 ### resolve_question
 ```
-npx tsx packages/shared/tools/resolve_question.ts <id> --project-id <project_id> --question "..." --answer "..."
+pnpm tsx packages/shared/tools/resolve_question.ts <id> --project-id <project_id> --question "..." --answer "..."
 ```
 
 ### get_gaps
 ```
-npx tsx packages/shared/tools/get_gaps.ts --project-id <project_id>
+pnpm tsx packages/shared/tools/get_gaps.ts --project-id <project_id>
 ```
 
 ### get_status
 ```
-npx tsx packages/shared/tools/get_status.ts --project-id <project_id>
+pnpm tsx packages/shared/tools/get_status.ts --project-id <project_id>
 ```
 
 ## Rules

package/templates/skills/assistkick-developer/SKILL.md

@@ -7,42 +7,46 @@ description: Implement features from the specification knowledge graph following
 
 ## Your Role
 You are a developer implementing features from a specification knowledge graph.
-Your goal is to pick up features from the kanban board, implement them following
-the project's coding standards, and move them through the pipeline. You interact
-with the project spec and kanban exclusively through the tools below.
+Your goal is to pick up features from the kanban board and implement them following
+the project's coding standards. You interact with the project spec and kanban
+exclusively through the tools below.
 
-All tools live in `assistkick-product-system/packages/shared/tools/` and are run with `npx tsx`.
+All tools live in `assistkick-product-system/packages/shared/tools/` and are run with `pnpm tsx`.
 
 ## References
 - For React development best practices, see [react_development_guidelines.md](references/react_development_guidelines.md)
 
+## CRITICAL RESTRICTIONS
+
+### NO Git Operations
+**You MUST NEVER run any git commands.** This is absolutely forbidden.
+Do not run `git commit`, `git push`, `git pull`, `git add`, `git checkout`,
+`git stash`, `git merge`, `git rebase`, or any other git command.
+The workflow engine handles all git operations automatically.
+
+### NO Kanban Card Transitions
+**You MUST NEVER use `move_card` to move features between kanban columns.**
+Do not move cards to `in_progress`, `in_review`, or any other column.
+The workflow engine handles all card transitions automatically.
+
 ## Session Start Protocol
 1. Call `get_status` — understand current project state
-2. Call `get_kanban --column todo` — identify which features are available to implement
-3. Pick the next `todo` feature to implement (prefer lowest feat_id first)
-4. Call `get_node` on the feature — read its full spec, acceptance criteria, and relations
-5. Call `get_node` on each connected node from the Relations section to understand the full context
-6. Call `move_card <feat_id> in_progress` to claim the feature
-7. State what you're implementing this session
+2. Call `get_kanban --column in_progress` — identify the feature assigned to you
+3. Call `get_node` on the feature — read its full spec, acceptance criteria, and relations
+4. Call `get_node` on each connected node from the Relations section to understand the full context
+5. State what you're implementing this session
 
 ## During Implementation
 - Before writing code → `get_node` on the feature shows its relations; call `get_node` on each connected node to understand the full context
 - Follow the development guidelines in `nfr_001` — ES modules, arrow functions in classes, dependency injection, single responsibility, no global state
 - Write tests using `node:test` — test data transformations and logic, not rendering
-- When implementation is complete → call `move_card <feat_id> in_review`
 - If you discover a spec gap or ambiguity → `update_node` to add an open question, then ask the user
 
-## Kanban Card Transitions
-Your transitions:
-- **Todo → In Progress**: When you start working on a feature
-- **In Progress → In Review**: When implementation is complete and tests pass
-
 ## Handling Rejections
 Features may be sent back to `todo` with rejection notes:
 1. Call `get_kanban` — check for rejection notes on the card
 2. Call `get_node` on the feature — understand the original spec and any notes
 3. Address all rejection notes in your implementation
-4. Move to `in_progress`, then `in_review` when fixed
 
 ## Development Guidelines (nfr_001)
 
@@ -87,47 +91,39 @@ Use the same `<project_id>` on **every** tool call in this session.
 
 ### get_kanban
 ```
-npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id>                    # show all columns
-npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column todo      # only todo items
-npx tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column qa        # only qa items
-```
-
-### move_card
-```
-npx tsx packages/shared/tools/move_card.ts <feature_id> <target_column> --project-id <project_id>
+pnpm tsx packages/shared/tools/get_kanban.ts --project-id <project_id>                    # show all columns
+pnpm tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column todo      # only todo items
+pnpm tsx packages/shared/tools/get_kanban.ts --project-id <project_id> --column qa        # only qa items
 ```
-Your allowed transitions:
-- `todo` → `in_progress`
-- `in_progress` → `in_review`
 
 ### start_session
 ```
-npx tsx packages/shared/tools/start_session.ts --project-id <project_id>
+pnpm tsx packages/shared/tools/start_session.ts --project-id <project_id>
 ```
 
 ### end_session
 ```
-npx tsx packages/shared/tools/end_session.ts --project-id <project_id> --summary "..." --nodes-touched "feat_001,dec_001" --questions-resolved 3
+pnpm tsx packages/shared/tools/end_session.ts --project-id <project_id> --summary "..." --nodes-touched "feat_001,dec_001" --questions-resolved 3
 ```
 
 ### search_nodes
 ```
-npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --query "keyword"
-npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --type feature
-npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --has-open-questions
-npx tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --completeness-below 0.5
+pnpm tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --query "keyword"
+pnpm tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --type feature
+pnpm tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --has-open-questions
+pnpm tsx packages/shared/tools/search_nodes.ts --project-id <project_id> --completeness-below 0.5
 ```
 
 ### get_node
 ```
-npx tsx packages/shared/tools/get_node.ts <node_id> --project-id <project_id>
-npx tsx packages/shared/tools/get_node.ts --name "Node Name" --project-id <project_id>
+pnpm tsx packages/shared/tools/get_node.ts <node_id> --project-id <project_id>
+pnpm tsx packages/shared/tools/get_node.ts --name "Node Name" --project-id <project_id>
 ```
 Returns the node content (formatted as markdown) plus a Relations section listing all connected nodes with direction, relation type, name, type, and status.
 
 ### add_node
 ```
-npx tsx packages/shared/tools/add_node.ts --project-id <project_id> --type <type> --name "Name" --description "..."
+pnpm tsx packages/shared/tools/add_node.ts --project-id <project_id> --type <type> --name "Name" --description "..."
 ```
 Valid types: feature, component, data_entity, decision, tech_choice,
 non_functional_requirement, design_token, design_pattern, user_role,
@@ -135,23 +131,23 @@ flow, assumption, open_question
 
 ### update_node
 ```
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-acceptance-criteria "..."
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-open-question "..."
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-note "Session N: ..."
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-status <draft|partially_defined|defined>
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-priority <low|medium|high|blocking>
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-description "..."
-npx tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-section "SectionName=content"
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-acceptance-criteria "..."
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-open-question "..."
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --add-note "Session N: ..."
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-status <draft|partially_defined|defined>
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-priority <low|medium|high|blocking>
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-description "..."
+pnpm tsx packages/shared/tools/update_node.ts <id> --project-id <project_id> --set-section "SectionName=content"
 ```
 
 ### resolve_question
 ```
-npx tsx packages/shared/tools/resolve_question.ts <id> --project-id <project_id> --question "..." --answer "..."
+pnpm tsx packages/shared/tools/resolve_question.ts <id> --project-id <project_id> --question "..." --answer "..."
 ```
 
 ### add_edge
 ```
-npx tsx packages/shared/tools/add_edge.ts <from_id> <relation> <to_id> --project-id <project_id>
+pnpm tsx packages/shared/tools/add_edge.ts <from_id> <relation> <to_id> --project-id <project_id>
 ```
 Valid relations: contains, depends_on, governed_by, constrained_by,
 implemented_with, reads_writes, exposes, consumes, performed_by,
@@ -159,35 +155,35 @@ escalates_to, relates_to
 
 ### remove_edge
 ```
-npx tsx packages/shared/tools/remove_edge.ts <from_id> <relation> <to_id> --project-id <project_id>
+pnpm tsx packages/shared/tools/remove_edge.ts <from_id> <relation> <to_id> --project-id <project_id>
 ```
 
 ### get_gaps
 ```
-npx tsx packages/shared/tools/get_gaps.ts --project-id <project_id>
-npx tsx packages/shared/tools/get_gaps.ts --project-id <project_id> --blocking-only
-npx tsx packages/shared/tools/get_gaps.ts --project-id <project_id> --type feature
+pnpm tsx packages/shared/tools/get_gaps.ts --project-id <project_id>
+pnpm tsx packages/shared/tools/get_gaps.ts --project-id <project_id> --blocking-only
+pnpm tsx packages/shared/tools/get_gaps.ts --project-id <project_id> --type feature
 ```
 
 ### get_status
 ```
-npx tsx packages/shared/tools/get_status.ts --project-id <project_id>
+pnpm tsx packages/shared/tools/get_status.ts --project-id <project_id>
 ```
 
 ### rebuild_index
 ```
-npx tsx packages/shared/tools/rebuild_index.ts --project-id <project_id>
-npx tsx packages/shared/tools/rebuild_index.ts --project-id <project_id> --dry-run
+pnpm tsx packages/shared/tools/rebuild_index.ts --project-id <project_id>
+pnpm tsx packages/shared/tools/rebuild_index.ts --project-id <project_id> --dry-run
 ```
 
 ## Rules
-1. All graph data is stored in SQLite (via Drizzle ORM) — always use the tools above to read and write data
-2. Always call `get_node` on a feature AND its related nodes before implementing — understand the full context
-3. Always use `get_kanban` to check kanban state and `move_card` to transition cards
-4. Call `move_card <feat_id> in_progress` before starting work, `move_card <feat_id> in_review` when done
-5. Follow all coding standards from `nfr_001` — arrow functions, DI, single responsibility, node:test
-6. Write tests for every feature — test logic and data transformations
-7. If a spec is ambiguous, add an open question to the node and ask the user — do not guess
-8. Check for rejection notes when picking up a feature that was sent back to todo
-9. All tool commands must be run from the `assistkick-product-system/` directory
-10. The `move_card` tool validates transitions — trust the error if a move is rejected
+1. **NEVER run git commands** — no commit, push, pull, add, checkout, or any git operation
+2. **NEVER use `move_card`** — do not move features between kanban columns; the workflow engine handles transitions
+3. All graph data is stored in SQLite (via Drizzle ORM) — always use the tools above to read and write data
+4. Always call `get_node` on a feature AND its related nodes before implementing — understand the full context
+5. Use `get_kanban` to check kanban state (read-only)
+6. Follow all coding standards from `nfr_001` — arrow functions, DI, single responsibility, node:test
+7. Write tests for every feature — test logic and data transformations
+8. If a spec is ambiguous, add an open question to the node and ask the user — do not guess
+9. Check for rejection notes when picking up a feature that was sent back to todo
+10. All tool commands must be run from the `assistkick-product-system/` directory