Initial commit

commands/generate-n-plans.md

@@ -0,0 +1,15 @@
+---
+argument-hint: [amount] [feature-id]
+description: Create n  amount of plans for a feature
+---
+
+THINK HARD.
+
+Generate $1 amount of plans for a feature with id $2, you'll use a sub-agent to generate each plan so that each plan is unique.
+
+A research file has already been gerated by a human or agent. Read it from .claude/research/[$2].md. If you can't find the research file, ask the user to provide the research.
+
+Then, think of n directions for the plans. Just think of the main directions, don't go into the details yet.
+Then, trigger a sub-agent for each direction to generate a plan. The sub-agent will use the research from .claude/research/[$2].md to generate the plan.
+
+Once you have generated all the plans, return the plans in a file called .claude/plans/[$2].md, adding a comparison of the plans at the end.

commands/implement-plan.md

@@ -0,0 +1,28 @@
+---
+argument-hint: [plan-id] [approach-id]
+description: Implement a plan for a feature
+---
+
+Implement the plan that can be found in .claude/plans/[$1].md, if you can't find the plan, ask the user to provide the plan.
+
+Inside of the plan there might be more than one approach, implement the one with id $2, if you can't find the approach, ask the user to provide the approach.
+
+**[IMPORTANT] Git Worktree**
+- Create a new worktree before starting to make changes.
+- Use command `git worktree add .tree/[$1]-[$2]-claude-implementation -b claude/[$1]-[$2]`.
+- ONLY USE THE WORKTREE FOR THE IMPLEMENTATION.
+
+**Process**
+1- Ask the user if he wants to add details or changes to the plan.
+2- Generate the todo list for the plan.
+3- Implement the fisrt item of the todo list.
+4- Ask the user for feedback.
+5- Commit the changes (DON'T PUSH THEM).
+6- Repeat the process until the plan is implemented.
+
+**IMPORTANT**
+- Stick to the plan and the approach, don't start free styling.
+- NEVER PUSH THE CHANGES.
+- Don't test.
+- Don't lint.
+- Don't tscheck the code.

commands/research-feature.md

@@ -0,0 +1,20 @@
+---
+argument-hint: [feature-id]
+description: Research a feature and generate a file with hints for the planning agent
+---
+
+Read the initial research file in .claude/features/[$1].md that contains the feature description provided by the user.
+
+If you can't find the feature file, ask the user to provide the feature description.
+
+Then, research the codebase for usefull information about the feature:
+
+- If there are existing implementations, you can use them as a reference.
+- If there are libraries or frameworks that can be used, you can use them as a reference.
+- If there are README.md files that describe usefull information about the feature, you can use them as a reference.
+
+(Reference document pahts, don't copy over the code).
+
+DON'T PROPOSE ANYTHING. NO ESTIMATES. NO PLANS. NO IMPLEMENTATIONS. NO CODE. JUST RESEARCH. DON'T TRY TO TELL THE NEXT AGENT WHAT TO DO, HE KNOWS. NO TODOs.
+
+Once you have gathered all the information, return the research in a file called .claude/research/[$1].md.