diff --git a/README.md b/README.md
index 39fb497..07d7992 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# git-pad
+# git-issue
 
 ## Philosophy
 
@@ -7,21 +7,6 @@
 
 * No staginag area
   * commit = add + commit (in git) 
-
-## gissue
-
-* Git-Embedded Distributed Issues Management System
-  * `git-issue` : dispatcher for commands like `git issue init`, `git issue new`, etc.
-    * `git-issue-mvp` : functions like `git_issue_init`
-    * `new_filename.sh` 
-      * `gen_repo_id` : random 6 alphabets
-      * `repo_id_in_use $1` : check if `$1` is used in any issue file
-      * `next_seq KSTEDF .md` : `KSTEDF-nnnn.md`라는 파일 형식에서 가장 마지막 `nnnn` 다음 
-      * `new_filename .md` : `.md` 파일에서 새로운 파일 이름
-
-* GitHub-Issues
-  * `injest.sh`
-  * `state.json`
   
 ## Design
 
@@ -32,37 +17,79 @@
   * No another independent repository(main point of git-native issue tracking tool)
 * Issues reside in a seperate folder and have different isolated history
   * Using custom ref, issue-ref would not be shown in `git branch`
+  * Using worktree, you can do whatever git commands in the linked worktree(eg. .issues/)
   * Issues isolated from codes
+* Issue file names are simple and readable
+  * Most hash or ULID, UUID are long and hard to read
+  * Intentionally choose to use sequence with repo ID(which is random 6 alphabets) (eg. `ABCDEF-000001`)
 * Issues, comments are markdown files
   * Easy to create, modify
+    * You can add custom fields in addition to `title:`, `status:`, etc.
   * Easy to search and custom advanced search is possible(using other tools of your choice)
     * issues are just markdown files so you can go into the folder and use `grep`, `ag`, `rg`, etc. if you need.
+* Commands are just like git
+  * most commands work like git(status/commit/push/fetch/merge) except for
+    * no staging area, so no add
+    * no push --force, push --force-with-lease
+      * intentionally no re-writing history
 * Minimal dependency
   * in bash scripts
   * No server-side setup required
   * lightweight
+* Freedom to customize
+  * You can use pre-commit, post-commit hooks.
+    * eg. Use AI API to polish issues
   
 ## Usage
 
-```
+```{bash}
 PATH=$PATH:$(pwd)  # replace $(pwd) with the directory name where git-pad, git-pad-func.sh live
 git issue init # or git issue clone if there is already remote 
 git issue list
 # A
+
+git issue show $ISSUE_ID
+git issue comment $ISSUE_ID
+
 git issue new # or git issue edit $ISSUE_ID
+git issue edit $ISSUE_ID
 git issue comment $ISSUE_ID
 git issue status
 git issue commit
-git issue push
+
 git issue fetch
 git issue merge
+# When conflicts, git issue edit $ISSUE_ID
+git issue push
+
 git issue list
 # goes to A
 ```
+
+## Implementation detail
+
+* Git-Embedded Distributed Issues Management System
+  * `git-issue` : dispatcher for commands like `git issue init`, `git issue new`, etc.
+    * `git-issue-mvp` : functions like `git_issue_init`
+    * `new_filename.sh` 
+      * `gen_repo_id` : random 6 alphabets
+      * `repo_id_in_use $1` : check if `$1` is used in any issue file
+      * `next_seq KSTEDF .md` : `KSTEDF-nnnn.md`라는 파일 형식에서 가장 마지막 `nnnn` 다음 
+      * `new_filename .md` : `.md` 파일에서 새로운 파일 이름
+
+* GitHub-Issues
+  * `gh_list_download.sh` : download github issue list 
+    * Forward time slice scan first, then Backward time slice scan.
+  * `gh_list_state.json`
+    * Stores the coverage of github issues updates
+
   
 ## Related Projects(as-of 2026.02.04)
 
 * [git-appraise](https://github.com/google/git-appraise)
+  * uses Git Notes, a built-in Git feature for attaching metadata to commits without modifying the commits themselves.
+    * Not easy to modify, search(use `git grep`) 
+  * Implemented in Go, requires Go tools installed.
   * latest release : 2021.04.23
 * [BE(Bugs-Everywhere)](https://github.com/aaiyer/bugseverywhere)
   * issues dependent on a branch
@@ -71,16 +98,25 @@ git issue list
 * [git-issue](https://github.com/dspinellis/git-issue)
   * independent repository
   * implemented in bash
+  * latest commit : 4 months ago
 * [git-bug](https://github.com/git-bug/git-bug)
   * custom reference 
     * `git log` gets messy as the number of bugs increases
       * IDE git history looks messy(eg. VSCode)
     * `git gc` or `git fsck` gets slower
+  * latest release : 2025.05.19
 * [git-dit](https://github.com/git-dit/git-dit)
   * issues are represented by empty commits(No file changes)
   * issue-commits using git's ref(`refs/dit`)
   * latest release(0.4.0) : 2017.09.15
+* [git-track](https://github.com/dhesse/Git-Track)
+  * no git-native, local(cannot be shared using git)
+  * latest commit : 15 years ago
 
-## Promotion
+## Discussion about git-native issue tracking tools
 
-* 
+* [reddit/git](https://www.reddit.com/r/git/)
+* [reddit: Decentralized Issue Tracking](https://www.reddit.com/r/programming/comments/4od2ni/decentralized_issue_tracking/)
+* [reddit: What is your simple issue tracking system](https://www.reddit.com/r/git/comments/wg6mk6/what_is_your_simple_issue_tracking_system/)
+* [StackOverflow: Is possible to store repository issues in the git repository?](https://stackoverflow.com/questions/19938579/is-possible-to-store-repository-issues-in-the-git-repository)
+* [StackOverflow: Keeping track of To-Do and issues in Git](https://stackoverflow.com/questions/7060973/keeping-track-of-to-do-and-issues-in-git)