Breakdown is a development instruction language tool for AI automated development using TypeScript and JSON/YAML/Markdown.
BreakDown is a prompt generation tool for AI development support. It generates prompts in a format that AI can easily understand, based on input Markdown files and specified conditions. The generated prompts function as instructions for AI systems to perform actual conversion and analysis.
Key Features:
Prompt Generation Process
When executed from the command line, it simply receives prompts.
sequenceDiagram
participant Developer as App Developer
participant Breakdown as Breakdown Tool
participant Files as File System
Developer->>Developer: Write project overview and requirements in Markdown
Developer->>Breakdown: Execute command (e.g., breakdown to project)
Breakdown->>Files: Identify required files
Note over Breakdown,Files: - Prompt files<br>- JSON Schema<br>- Input/output paths
Files->>Breakdown: Load files
Breakdown->>Breakdown: Prompt generation process
Note over Breakdown: - Prompt selection<br>- Variable replacement<br>- Schema application
Breakdown->>Developer: Output generated prompt
The terminal command → prompt part can be run on AI development agents. The goal is to generate recursive instructions based on these instructions.
AI Processing Process
The basic structure is simple. By establishing a process to generate prompts for AI automated development, instructions are automatically given. Instructions create new subdivided instructions, which are then used for the next instructions.
sequenceDiagram
participant Developer as App Developer
participant AI as AI Development Agent
participant Breakdown as breakdown command
participant Result as Processing Result
loop Repetition of instruction, prompt generation, and AI processing
Developer->>AI: Input new instruction
AI->>Breakdown: Execute breakdown command based on instruction
Breakdown->>AI: Output generated prompt
AI->>AI: Process based on prompt
Note over AI: - Markdown analysis<br>- Structuring<br>- Task breakdown
AI->>Result: Output processing result
Result->>Developer: Receive result
Developer->>Developer: Result = new instruction
end
Internal Processing
Uses pre-prepared prompts. Selects appropriate prompts from commands and treats parameter values as variables to embed them.
Number of combinations:
This combination number is multiplied by the versatility of LLM, making it prone to divergence.
When considering development products as deliverables, methods to control divergence and converge toward objectives are necessary. Also, since specification definition and breakdown methods required for development have accumulated theories, they become finite patterns. (For example, the 23 design patterns in GoF.)
Therefore, Schema definitions are used to guide diverse expressions into specific patterns.
The Breakdown tool predefines three layers: Project > Issues > Tasks, and the to instruction performs breakdown.
At this stage, pre-prepared prompts are classified into either project/issue/task.
When multiplying the combinations of input → breakdown destination (output), 5 combination patterns (P->I,T, I->I,T, T->T) are pre-prepared.
For cases different from the breakdown direction, the summary instruction performs summary direction (project -> Project, Issues -> Project, etc.).
In particular, the defect instruction is provided to respond to error handling, bug response, and requests for undeveloped states. For details, see Usage.
Making the prompt selection part AI-powered would make it more dynamic. Since this part would be more efficient using external services, it can also be separated from this tool.
JSON Schema references are used to converge to finite patterns. The goal is to control generation results by referencing Schema definitions as checklists rather than fitting them into Schema definitions. The final output does not need to be JSON. More versatile YAML/Markdown/Text is assumed.
In upcoming versions, it is planned to enable Schema reference based on URLs. This will enable data processing using Schema.org and utilization of other Schema definitions.
If there are appropriate Schema definitions for development requirement definitions, they will be referenced, but since none have been found yet, we plan to create what this application requires.
| English | 日本語 |