Merge pull request #387 from dexhorthy/prompts

some dumb vibe-y prompt tweaks
This commit is contained in:
Dex
2025-07-31 14:00:01 -07:00
committed by GitHub
6 changed files with 50 additions and 26 deletions

View File

@@ -178,6 +178,10 @@ After structure approval:
[What exists now, what's missing, key constraints discovered]
## Desired End State
[A Specification of the desired end state after this plan is complete, and how to verify it]
### Key Discoveries:
- [Important finding with file:line reference]
- [Pattern to follow]

View File

@@ -1,9 +1,18 @@
## PART I - IF A TICKET IS MENTIONED
0c. use `linear` cli to fetch the selected item into thoughts with the ticket number - ./thoughts/shared/tickets/ENG-xxxx.md
0d. read the ticket and all comments to understand the implementation plan and any concerns
## PART I - IF NO TICKET IS MENTIOND
0. read .claude/commands/linear.md
0a. fetch the top 10 priority items from linear in status "ready for dev" using the MCP tools, noting all items in the `links` section
0b. select the highest priority SMALL or XS issue from the list (if no SMALL or XS issues exist, EXIT IMMEDIATELY and inform the user)
0c. use `linear` cli to fetch the selected item into thoughts with the ticket number - ./thoughts/shared/tickets/ENG-xxxx.md
0d. read the ticket and all comments to understand the implementation plan and any concerns
## PART II - NEXT STEPS
think deeply
1. move the item to "in dev" using the MCP tools
@@ -13,10 +22,7 @@ think deeply
think deeply about the implementation
2. set up worktree for implementation:
2a. create a new worktree with the Linear branch name: `git worktree add -b BRANCH_NAME ~/wt/humanlayer/ENG-XXXX`
2b. copy `.claude/settings.local.json` to the worktree directory
2c. run `make -C ~/wt/humanlayer/ENG-XXXX setup` to install dependencies
2d. run `make -C ~/wt/humanlayer/ENG-XXXX thoughts` to setup thoughts
2e. launch implementation session: `npx humanlayer launch --model opus -w ~/wt/humanlayer/ENG-XXXX "/implement_plan and when you are done implementing and all tests pass, read ./claude/commands/commit.md and create a commit, then read ./claude/commands/describe_pr.md and create a PR, then add a comment to the Linear ticket with the PR link"`
2a. read `hack/create_worktree.sh` and create a new worktree with the Linear branch name: `./hack/create_worktree.sh ENG-XXXX BRANCH_NAME`
2b. launch implementation session: `npx humanlayer launch --model opus -w ~/wt/humanlayer/ENG-XXXX "/implement_plan and when you are done implementing and all tests pass, read ./claude/commands/commit.md and create a commit, then read ./claude/commands/describe_pr.md and create a PR, then add a comment to the Linear ticket with the PR link"`
think deeply, use TodoWrite to track your tasks. When fetching from linear, get the top 10 items by priority but only work on ONE item - specifically the highest priority SMALL or XS sized issue.

View File

@@ -1,12 +1,22 @@
## PART I - IF A TICKET IS MENTIONED
0c. use `linear` cli to fetch the selected item into thoughts with the ticket number - ./thoughts/shared/tickets/ENG-xxxx.md
0d. read the ticket and all comments to learn about past implementations and research, and any questions or concerns about them
### PART I - IF NO TICKET IS MENTIONED
0. read .claude/commands/linear.md
0a. fetch the top 10 priority items from linear in status "ready for spec" using the MCP tools, noting all items in the `links` section
0b. select the highest priority SMALL or XS issue from the list (if no SMALL or XS issues exist, EXIT IMMEDIATELY and inform the user)
0c. use `linear` cli to fetch the selected item into thoughts with the ticket number - ./thoughts/shared/tickets/ENG-xxxx.md
0d. read the ticket and all comments to learn about past implementations and research, and any questions or concerns about them
### PART II - NEXT STEPS
think deeply
1. move the item to "spec in progress" using the MCP tools
1. move the item to "plan in progress" using the MCP tools
1a. read ./claude/commands/create_plan.md
1b. determine if the item has a linked implementation plan document based on the `links` section
1d. if the plan exists, you're done, respond with a link to the ticket
@@ -15,6 +25,6 @@ think deeply
think deeply
2. when the plan is complete, `humanlayer thoughts sync` and attach the doc to the ticket using the MCP tools and create a terse comment with a link to it (re-read .claude/commands/linear.md if needed)
2a. move the item to "spec in review" using the MCP tools
2a. move the item to "plan in review" using the MCP tools
think deeply, use TodoWrite to track your tasks. When fetching from linear, get the top 10 items by priority but only work on ONE item - specifically the highest priority SMALL or XS sized issue.

View File

@@ -1,9 +1,18 @@
0. read .claude/commands/linear.md
0a. fetch the top 10 priority items from linear in status "research needed" using the MCP tools, noting all items in the `links` section
0b. select the highest priority issue from the list
## PART I - IF A LINEAR TICKET IS MENTIONED
0c. use `linear` cli to fetch the selected item into thoughts with the ticket number - ./thoughts/shared/tickets/ENG-xxxx.md
0d. read the ticket and all comments to understand what research is needed and any previous attempts
## PART I - IF NO TICKET IS MENTIONED
0. read .claude/commands/linear.md
0a. fetch the top 10 priority items from linear in status "research needed" using the MCP tools, noting all items in the `links` section
0b. select the highest priority SMALL or XS issue from the list (if no SMALL or XS issues exist, EXIT IMMEDIATELY and inform the user)
0c. use `linear` cli to fetch the selected item into thoughts with the ticket number - ./thoughts/shared/tickets/ENG-xxxx.md
0d. read the ticket and all comments to understand what research is needed and any previous attempts
## PART II - NEXT STEPS
think deeply
1. move the item to "research in progress" using the MCP tools
@@ -18,7 +27,8 @@ think deeply about the research needs
2c. search the codebase for relevant implementations and patterns
2d. examine existing similar features or related code
2e. identify technical constraints and opportunities
2f. document findings in a new thoughts document: `thoughts/shared/research/ENG-XXXX_research.md`
2f. Be unbiased - don't think too much about an ideal implementation plan, just document all related files and how the systems work today
2g. document findings in a new thoughts document: `thoughts/shared/research/ENG-XXXX_research.md`
think deeply about the findings
@@ -31,6 +41,6 @@ think deeply about the findings
4. update the ticket:
4a. attach the research document to the ticket using the MCP tools with proper link formatting
4b. add a comment summarizing the research outcomes
4c. move the item to "ready for spec" using the MCP tools
4c. move the item to "research in review" using the MCP tools
think deeply, use TodoWrite to track your tasks. When fetching from linear, get the top 10 items by priority but only work on ONE item - specifically the highest priority issue.

View File

@@ -29,9 +29,14 @@ BASE_BRANCH=${2:-$(git branch --show-current)}
# Get base directory name (should be 'humanlayer')
REPO_BASE_NAME=$(basename "$(pwd)")
# Construct paths
WORKTREE_DIR_NAME="${REPO_BASE_NAME}_${WORKTREE_NAME}"
WORKTREES_BASE="$HOME/.humanlayer/worktrees"
if [ ! -z "$HUMANLAYER_WORKTREE_OVERRIDE_BASE" ]; then
WORKTREE_DIR_NAME="${WORKTREE_NAME}"
WORKTREES_BASE="${HUMANLAYER_WORKTREE_OVERRIDE_BASE}/${REPO_BASE_NAME}"
else
WORKTREE_DIR_NAME="${REPO_BASE_NAME}_${WORKTREE_NAME}"
WORKTREES_BASE="$HOME/.humanlayer/worktrees"
fi
WORKTREE_PATH="${WORKTREES_BASE}/${WORKTREE_DIR_NAME}"
echo "🌳 Creating worktree: ${WORKTREE_NAME}"

View File

@@ -1,11 +0,0 @@
0. read the current code in @hlyr, @hld, @humanlayer-wui, and @claudecode-go
0a. review the structure of the thoughts/ directory
0b. review the @ARCHITECTURE_IMPROVEMENTS_PLAN.md
0c. run the tests with `make check test` so you know if they are passing or not
1. pick the highest priority item @ARCHITECTURE_IMPROVEMENTS_PLAN.md and implement it using up to 500 subagents, including robust unit and integration tests, and updating or even (rarely) removing the existing tests as appropriate, until all tests are passing
2. test your changes and esnure they are working `make check test`
3. update the @ARCHITECTURE_IMPROVEMENTS_PLAN.md with your changes and commit all changes with git commit -a -m "your message" according to .claude/commands/commit.md