@jakkrichm/create-nexus-devflow 2.0.1 → 2.0.2

package/template/.agents/skills/obsidian-clipper-template-creator/references/json-schema.md

@@ -1,77 +0,0 @@
-# Obsidian Web Clipper JSON Schema
-
-The Obsidian Web Clipper imports templates via JSON files.
-
-## Root Structure
-
-```json
-{
-	"schemaVersion": "0.1.0",
-	"name": "Template Name",
-	"behavior": "create",
-	"noteContentFormat": "Markdown content here...",
-	"properties": [],
-	"triggers": [],
-	"noteNameFormat": "{{title}}",
-	"path": "Inbox/"
-}
-```
-
-### Fields
-
-*   **`schemaVersion`**: Always "0.1.0".
-*   **`name`**: The display name of the template in the Clipper.
-*   **`behavior`**: How the note is created.
-    *   `create`: Create a new note.
-    *   `append-specific`: Append to a specific note (requires `path` to be a full file path).
-    *   `append-daily`: Append to the daily note.
-*   **`noteContentFormat`**: The body of the note.
-    *   Use `\n` for newlines.
-    *   Can use all variables (e.g., `{{content}}`, `{{selection}}`).
-    *   Supports **template logic** (conditionals, loops, variable assignment) as documented in [logic.md](logic.md).
-*   **`noteNameFormat`**: The filename pattern (e.g., `{{date}} - {{title}}`).
-*   **`path`**: The location to save the note.
-    *   For `create` behavior: The *folder* to save the note in (e.g., `Clippings/` or `Recipes/`).
-    *   For `append-specific` behavior: The *full file path* of the note to append to (e.g., `Databases/Recipes.md`).
-*   **`triggers`**: Array of strings to automatically select this template.
-    *   **URL Patterns**: `["https://www.youtube.com/watch"]` (Simple string or Regex).
-    *   **Schema Types**: `["schema:Recipe"]` (Triggers if the page contains this Schema.org type).
-
-## Properties
-
-The `properties` array defines the YAML frontmatter of the note.
-
-```json
-"properties": [
-    {
-        "name": "category",
-        "value": "Recipes",
-        "type": "text"
-    },
-    {
-        "name": "published",
-        "value": "{{published}}",
-        "type": "datetime"
-    }
-]
-```
-
-### Property Types
-
-*   **`text`**: Simple text string.
-*   **`multitext`**: List of text strings (for tags/aliases).
-*   **`number`**: Numeric value.
-*   **`checkbox`**: Boolean true/false.
-*   **`date`**: Date string (YYYY-MM-DD).
-*   **`datetime`**: Date and time string.
-
-### Property Object Structure
-
-*   **`name`**: The key in the YAML frontmatter.
-*   **`value`**: The value to populate. Can contain variables and the same **template logic** (conditionals, loops, variable assignment) as `noteContentFormat`; see [logic.md](logic.md).
-*   **`type`**: One of the types listed above.
-
-## Template validation
-
-The Clipper template editor checks template syntax. 
-Invalid logic in `noteContentFormat` or property `value` fields will be reported in the editor; use valid syntax as described in the [Logic](https://help.obsidian.md/web-clipper/logic) documentation.

package/template/.agents/skills/obsidian-clipper-template-creator/references/logic.md

@@ -1,67 +0,0 @@
-# Obsidian Web Clipper Template Logic
-
-**Official docs:** [Logic - Obsidian Help](https://help.obsidian.md/web-clipper/logic)
-
-As of **Obsidian Web Clipper 1.0.0**, templates support logic in `noteContentFormat` and in property `value` fields: conditionals, loops, variable assignment, and fallbacks. This page describes how each works. For authoritative syntax and delimiters, use the official documentation link above.
-
----
-
-## When to use logic
-
-- **Conditionals:** Show optional sections only when data exists (e.g. nutrition block only if `{{schema:Recipe:nutrition}}` is present).
-- **Variable assignment:** Assign a value once and reuse it in the template to avoid repeating long expressions.
-- **Fallbacks:** Provide a default when a variable is empty so the note still looks correct.
-- **Loops:** Iterate over arrays (ingredients, steps, tags) to format each item; combine with filters for list/table output.
-
-Keep simple templates simple; add logic only when it improves the result or avoids broken output for missing data.
-
----
-
-## Conditionals
-
-Conditionals include or exclude blocks based on whether a value exists or meets a condition.
-
-- **Comparison operators:** Compare two values (e.g. equals, not equals, greater than, less than). Exact operators are defined in the official Logic page.
-- **Logical operators:** Combine or negate conditions (e.g. and, or, not; or symbol forms like `&&`, `||`, `!`). Use these to build compound conditions.
-- **Truthiness:** Values are evaluated in a JavaScript-like way for conditions. Empty strings, empty arrays, and missing variables are typically falsy; non-empty values are truthy. See the official docs for the full rules.
-- **Typical use:** Wrap optional sections (e.g. author, nutrition, image) in a conditional so they only render when the variable has a value.
-
----
-
-## Assign a variable
-
-You can assign a variable once and reuse it in the same template. Use this to avoid repeating long variable or filter chains (e.g. the same schema path or selector used in multiple places). The assigned variable is available for the rest of the template in that scope. Exact syntax (e.g. assignment block format and scope) is in the official Logic documentation.
-
----
-
-## Fallbacks
-
-Fallbacks supply a default when a variable is empty.
-
-- **Default when missing:** Provide a fallback value so the template still produces readable output when the primary variable is empty.
-- **Chaining fallbacks:** You can chain multiple fallbacks (e.g. try variable A, then B, then a literal default). The first non-empty value is used.
-- **With filters:** Fallbacks can be used together with filters. The evaluation order (variable → fallback → filter, or other) is defined in the official docs under "With filters" and "Evaluation order."
-
----
-
-## Loops
-
-Loops iterate over array values (e.g. ingredients, instructions, tags).
-
-- **Loop sources:** The array to iterate over—typically a variable that returns a list (e.g. `{{schema:Recipe:recipeIngredient}}`, `{{schema:Recipe:recipeInstructions}}`).
-- **Loop variables:** Inside the loop you get a variable for the current item; you may also get an index or other loop metadata. Names and behavior are described in the official "Loop variables" and "Accessing array items by index" sections.
-- **Accessing array items by index:** When you need the nth item of an array outside a loop, or need the current index inside a loop, the syntax is defined in the official documentation.
-- **Nested loops:** Loops can be nested when you have arrays of structured data (e.g. steps each with sub-steps).
-- **Combine logic:** Loops and conditionals can be combined (e.g. loop over items and show a subsection only when a field exists, or conditionally include a loop).
-
----
-
-## Evaluation order and combining logic
-
-The order in which variables, filters, fallbacks, conditionals, and loops are evaluated is defined in the official documentation. When you combine logic (e.g. conditionals inside loops, or variables used in both conditionals and output), follow the official "Evaluation order" and "Combine logic" sections so behavior matches expectations.
-
----
-
-## Template validation
-
-The Obsidian Web Clipper template editor **validates template syntax**. Invalid logic (e.g. malformed conditionals or loops) will be reported in the editor. When generating templates, use only logic constructs and syntax described on the official Logic page so that the template passes validation.

package/template/.agents/skills/obsidian-clipper-template-creator/references/variables.md

@@ -1,64 +0,0 @@
-# Obsidian Web Clipper Variables
-
-**Official Docs:** [help.obsidian.md/web-clipper/variables](https://help.obsidian.md/web-clipper/variables)
-
-## Preset Variables
-Automatically extracted from the page.
-
-- `{{content}}`: Main article content (markdown).
-- `{{contentHtml}}`: Main article content (HTML).
-- `{{title}}`: Page title.
-- `{{url}}`: Page URL.
-- `{{author}}`: Author name.
-- `{{date}}`: Current date.
-- `{{published}}`: Publication date (if detected).
-- `{{site}}`: Site name.
-- `{{description}}`: Meta description.
-- `{{highlights}}`: Highlighted text (if any).
-- `{{selection}}`: Selected text.
-- `{{fullHtml}}`: Full page HTML.
-- `{{favicon}}`: Favicon URL.
-- `{{image}}`: Social share image URL.
-- `{{words}}`: Word count.
-- `{{domain}}`: Domain name.
-
-## Prompt Variables (AI)
-Use `{{"Your prompt here"}}` to ask the AI Interpreter to extract or summarize info.
-*Requires Interpreter to be enabled.*
-
-Examples:
-- `{{"Summarize in 3 bullet points"}}`
-- `{{"Extract the ingredients list"}}`
-- `{{"Translate to English"}}`
-
-## Selector Variables
-Extract content using CSS selectors.
-Syntax: `{{selector:css-selector}}` or `{{selector:css-selector?attribute}}`
-
-Examples:
-- `{{selector:h1}}`: Text of H1 tag.
-- `{{selector:img.hero?src}}`: Source of image with class 'hero'.
-- `{{selector:.author}}`: Text of element with class 'author'.
-- `{{selectorHtml:body|markdown}}`: Full HTML converted to markdown.
-
-## Meta Variables
-Extract data from meta tags.
-Syntax: `{{meta:name}}` or `{{meta:property}}`
-
-Examples:
-- `{{meta:description}}`
-- `{{meta:og:title}}`
-
-## Schema.org Variables
-Extract structured data.
-Syntax: `{{schema:Property}}` or `{{schema:@Type:Property}}`
-
-Examples:
-- `{{schema:Recipe:recipeIngredient}}`
-- `{{schema:author.name}}`
-- `{{schema:Article:headline}}`
-
-## Fallbacks
-When a variable is empty, you can supply a default value (fallback). 
-Fallbacks can be chained (try variable A, then B, then a literal default) and used with filters. 
-For syntax and evaluation order, see [logic.md](logic.md).

package/template/.agents/skills/obsidian-markdown/SKILL.md

@@ -1,205 +0,0 @@
----
-name: obsidian-markdown
-description: Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
-risk: unknown
-source: "https://github.com/kepano/obsidian-skills"
-date_added: "2026-03-21"
----
-
-# Obsidian Flavored Markdown Skill
-
-Create and edit valid Obsidian Flavored Markdown. Obsidian extends CommonMark and GFM with wikilinks, embeds, callouts, properties, comments, and other syntax. This skill covers only Obsidian-specific extensions -- standard Markdown (headings, bold, italic, lists, quotes, code blocks, tables) is assumed knowledge.
-
-## When to Use
-
-- Use when writing or editing Markdown notes intended for Obsidian.
-- Use when the task involves wikilinks, embeds, callouts, frontmatter properties, or Obsidian-specific syntax.
-- Use when the user wants notes that render correctly inside an Obsidian vault.
-
-## Workflow: Creating an Obsidian Note
-
-1. **Add frontmatter** with properties (title, tags, aliases) at the top of the file. See [PROPERTIES.md](references/PROPERTIES.md) for all property types.
-2. **Write content** using standard Markdown for structure, plus Obsidian-specific syntax below.
-3. **Link related notes** using wikilinks (`[[Note]]`) for internal vault connections, or standard Markdown links for external URLs.
-4. **Embed content** from other notes, images, or PDFs using the `![[embed]]` syntax. See [EMBEDS.md](references/EMBEDS.md) for all embed types.
-5. **Add callouts** for highlighted information using `> [!type]` syntax. See [CALLOUTS.md](references/CALLOUTS.md) for all callout types.
-6. **Verify** the note renders correctly in Obsidian's reading view.
-
-> When choosing between wikilinks and Markdown links: use `[[wikilinks]]` for notes within the vault (Obsidian tracks renames automatically) and plain Markdown links for external URLs only.
-
-## Internal Links (Wikilinks)
-
-```markdown
-[[Note Name]]                          Link to note
-[[Note Name|Display Text]]             Custom display text
-[[Note Name#Heading]]                  Link to heading
-[[Note Name#^block-id]]                Link to block
-[[#Heading in same note]]              Same-note heading link
-```
-
-Define a block ID by appending `^block-id` to any paragraph:
-
-```markdown
-This paragraph can be linked to. ^my-block-id
-```
-
-For lists and quotes, place the block ID on a separate line after the block:
-
-```markdown
-> A quote block
-
-^quote-id
-```
-
-## Embeds
-
-Prefix any wikilink with `!` to embed its content inline:
-
-```markdown
-![[Note Name]]                         Embed full note
-![[Note Name#Heading]]                 Embed section
-![[image.png]]                         Embed image
-![[image.png|300]]                     Embed image with width
-![[document.pdf#page=3]]               Embed PDF page
-```
-
-See [EMBEDS.md](references/EMBEDS.md) for audio, video, search embeds, and external images.
-
-## Callouts
-
-```markdown
-> [!note]
-> Basic callout.
-
-> [!warning] Custom Title
-> Callout with a custom title.
-
-> [!faq]- Collapsed by default
-> Foldable callout (- collapsed, + expanded).
-```
-
-Common types: `note`, `tip`, `warning`, `info`, `example`, `quote`, `bug`, `danger`, `success`, `failure`, `question`, `abstract`, `todo`.
-
-See [CALLOUTS.md](references/CALLOUTS.md) for the full list with aliases, nesting, and custom CSS callouts.
-
-## Properties (Frontmatter)
-
-```yaml
----
-title: My Note
-date: 2024-01-15
-tags:
-  - project
-  - active
-aliases:
-  - Alternative Name
-cssclasses:
-  - custom-class
----
-```
-
-Default properties: `tags` (searchable labels), `aliases` (alternative note names for link suggestions), `cssclasses` (CSS classes for styling).
-
-See [PROPERTIES.md](references/PROPERTIES.md) for all property types, tag syntax rules, and advanced usage.
-
-## Tags
-
-```markdown
-#tag                    Inline tag
-#nested/tag             Nested tag with hierarchy
-```
-
-Tags can contain letters, numbers (not first character), underscores, hyphens, and forward slashes. Tags can also be defined in frontmatter under the `tags` property.
-
-## Comments
-
-```markdown
-This is visible %%but this is hidden%% text.
-
-%%
-This entire block is hidden in reading view.
-%%
-```
-
-## Obsidian-Specific Formatting
-
-```markdown
-==Highlighted text==                   Highlight syntax
-```
-
-## Math (LaTeX)
-
-```markdown
-Inline: $e^{i\pi} + 1 = 0$
-
-Block:
-$$
-\frac{a}{b} = c
-$$
-```
-
-## Diagrams (Mermaid)
-
-````markdown
-```mermaid
-graph TD
-    A[Start] --> B{Decision}
-    B -->|Yes| C[Do this]
-    B -->|No| D[Do that]
-```
-````
-
-To link Mermaid nodes to Obsidian notes, add `class NodeName internal-link;`.
-
-## Footnotes
-
-```markdown
-Text with a footnote[^1].
-
-[^1]: Footnote content.
-
-Inline footnote.^[This is inline.]
-```
-
-## Complete Example
-
-````markdown
----
-title: Project Alpha
-date: 2024-01-15
-tags:
-  - project
-  - active
-status: in-progress
----
-
-# Project Alpha
-
-This project aims to [[improve workflow]] using modern techniques.
-
-> [!important] Key Deadline
-> The first milestone is due on ==January 30th==.
-
-## Tasks
-
-- [x] Initial planning
-- [ ] Development phase
-  - [ ] Backend implementation
-  - [ ] Frontend design
-
-## Notes
-
-The algorithm uses $O(n \log n)$ sorting. See [[Algorithm Notes#Sorting]] for details.
-
-![[Architecture Diagram.png|600]]
-
-Reviewed in [[Meeting Notes 2024-01-10#Decisions]].
-````
-
-## References
-
-- [Obsidian Flavored Markdown](https://help.obsidian.md/obsidian-flavored-markdown)
-- [Internal links](https://help.obsidian.md/links)
-- [Embed files](https://help.obsidian.md/embeds)
-- [Callouts](https://help.obsidian.md/callouts)
-- [Properties](https://help.obsidian.md/properties)

package/template/.agents/skills/obsidian-markdown/references/CALLOUTS.md

@@ -1,58 +0,0 @@
-# Callouts Reference
-
-## Basic Callout
-
-```markdown
-> [!note]
-> This is a note callout.
-
-> [!info] Custom Title
-> This callout has a custom title.
-
-> [!tip] Title Only
-```
-
-## Foldable Callouts
-
-```markdown
-> [!faq]- Collapsed by default
-> This content is hidden until expanded.
-
-> [!faq]+ Expanded by default
-> This content is visible but can be collapsed.
-```
-
-## Nested Callouts
-
-```markdown
-> [!question] Outer callout
-> > [!note] Inner callout
-> > Nested content
-```
-
-## Supported Callout Types
-
-| Type | Aliases | Color / Icon |
-|------|---------|-------------|
-| `note` | - | Blue, pencil |
-| `abstract` | `summary`, `tldr` | Teal, clipboard |
-| `info` | - | Blue, info |
-| `todo` | - | Blue, checkbox |
-| `tip` | `hint`, `important` | Cyan, flame |
-| `success` | `check`, `done` | Green, checkmark |
-| `question` | `help`, `faq` | Yellow, question mark |
-| `warning` | `caution`, `attention` | Orange, warning |
-| `failure` | `fail`, `missing` | Red, X |
-| `danger` | `error` | Red, zap |
-| `bug` | - | Red, bug |
-| `example` | - | Purple, list |
-| `quote` | `cite` | Gray, quote |
-
-## Custom Callouts (CSS)
-
-```css
-.callout[data-callout="custom-type"] {
-  --callout-color: 255, 0, 0;
-  --callout-icon: lucide-alert-circle;
-}
-```

package/template/.agents/skills/obsidian-markdown/references/EMBEDS.md

@@ -1,63 +0,0 @@
-# Embeds Reference
-
-## Embed Notes
-
-```markdown
-![[Note Name]]
-![[Note Name#Heading]]
-![[Note Name#^block-id]]
-```
-
-## Embed Images
-
-```markdown
-![[image.png]]
-![[image.png|640x480]]    Width x Height
-![[image.png|300]]        Width only (maintains aspect ratio)
-```
-
-## External Images
-
-```markdown
-![Alt text](https://example.com/image.png)
-![Alt text|300](https://example.com/image.png)
-```
-
-## Embed Audio
-
-```markdown
-![[audio.mp3]]
-![[audio.ogg]]
-```
-
-## Embed PDF
-
-```markdown
-![[document.pdf]]
-![[document.pdf#page=3]]
-![[document.pdf#height=400]]
-```
-
-## Embed Lists
-
-```markdown
-![[Note#^list-id]]
-```
-
-Where the list has a block ID:
-
-```markdown
-- Item 1
-- Item 2
-- Item 3
-
-^list-id
-```
-
-## Embed Search Results
-
-````markdown
-```query
-tag:#project status:done
-```
-````

package/template/.agents/skills/obsidian-markdown/references/PROPERTIES.md

@@ -1,61 +0,0 @@
-# Properties (Frontmatter) Reference
-
-Properties use YAML frontmatter at the start of a note:
-
-```yaml
----
-title: My Note Title
-date: 2024-01-15
-tags:
-  - project
-  - important
-aliases:
-  - My Note
-  - Alternative Name
-cssclasses:
-  - custom-class
-status: in-progress
-rating: 4.5
-completed: false
-due: 2024-02-01T14:30:00
----
-```
-
-## Property Types
-
-| Type | Example |
-|------|---------|
-| Text | `title: My Title` |
-| Number | `rating: 4.5` |
-| Checkbox | `completed: true` |
-| Date | `date: 2024-01-15` |
-| Date & Time | `due: 2024-01-15T14:30:00` |
-| List | `tags: [one, two]` or YAML list |
-| Links | `related: "[[Other Note]]"` |
-
-## Default Properties
-
-- `tags` - Note tags (searchable, shown in graph view)
-- `aliases` - Alternative names for the note (used in link suggestions)
-- `cssclasses` - CSS classes applied to the note in reading/editing view
-
-## Tags
-
-```markdown
-#tag
-#nested/tag
-#tag-with-dashes
-#tag_with_underscores
-```
-
-Tags can contain: letters (any language), numbers (not first character), underscores `_`, hyphens `-`, forward slashes `/` (for nesting).
-
-In frontmatter:
-
-```yaml
----
-tags:
-  - tag1
-  - nested/tag2
----
-```

package/template/.agents/skills/prompt-addons/SKILL.md

@@ -1,99 +0,0 @@
----
-name: prompt-addons
-description: Routes external prompt families into DevFlow 2.0 workflows, specialist agents, or thin skill aliases. Use when deciding whether a prompt-inspired behavior should become a mainline workflow, a companion command, a reusable skill, or remain legacy-only.
----
-
-# Prompt Addons
-
-Use this skill when adapting outside prompt patterns into the DevFlow 2.0 system.
-
-## Core Rule
-
-Adapt intent, not old output contracts.
-
-DevFlow 2.0 uses a stage-based, markdown-first model:
-
-1. Mainline workflow stays minimal and ordered
-2. Companion commands exist for non-mainline help
-3. Specialist agents and skills handle reusable methods
-4. JSON-first orchestration is legacy and should not define new architecture
-
-## Mainline Routing
-
-| Need | Route to |
-| :--- | :--- |
-| Explore problem space | `/00-Discover` |
-| Clarify goal, scope, decisions | `/10-Define` |
-| Lock delivery contract | `/20-Spec` |
-| Break into execution plan | `/30-Plan` |
-| Build the change | `/40-Implement` |
-| Validate quality and evidence | `/50-Verify` |
-| Package release-ready outcome | `/70-Release` |
-| Summarize the full run | `/60-Report` |
-
-## Companion Command Routing
-
-| Command | Use when | Typical stage pairing |
-| :--- | :--- | :--- |
-| `Brainstorm` | โจทย์ยังไม่นิ่ง ต้องคิดทางเลือกก่อน lock | Discover, Define |
-| `Research` | ต้องหาหลักฐานหรือข้อมูลเพิ่ม | Discover, Define, Spec, Verify |
-| `Debug` | งานผิดปกติ ต้องหา root cause | Implement, Verify |
-| `Preview` | ต้องตรวจชิ้นงานระหว่างทาง | Implement, Verify |
-| `Wiki` | ต้องสกัดความรู้ reusable | Verify, Release, Report |
-| `Help` | ผู้ใช้ไม่แน่ใจว่าจะเริ่มตรงไหน | ก่อนเข้า stage หรือระหว่างทาง |
-
-## Classification Rule
-
-ก่อนสร้าง workflow ใหม่ ให้จัดประเภทก่อน:
-
-1. ถ้า intent เปลี่ยน stage ของงาน ให้ route เข้าสู่ mainline stage ที่มีอยู่
-2. ถ้าเป็นวิธีทำงานที่ใช้ซ้ำหลาย stage ให้เป็น skill
-3. ถ้าเป็นความเชี่ยวชาญเฉพาะด้าน ให้เป็น agent
-4. ถ้าเป็นแค่ตัวช่วยคิดหรือหาหลักฐานระหว่างทาง ให้เป็น companion command
-5. ถ้าอิง dashboard/json orchestration เดิมเป็นหลัก ให้คงไว้เป็น legacy หรือ migration note
-
-## Prompt Family Routing
-
-| Family | DevFlow 2.0 route | Keep as |
-| :--- | :--- | :--- |
-| Spec | `/10-Define`, `/20-Spec`, `/30-Plan` | workflow + `requirements-engineer` |
-| Complexity | `/10-Define`, `/30-Plan` | workflow content, not standalone mainline |
-| Roadmap | Discover/Define adjacent | skill or optional workflow outside core line |
-| Ideation | `Brainstorm`, `Research` | companion command |
-| Competitor | `Research` during Discover/Define | companion command or research skill |
-| Insight | `Wiki`, `/60-Report` | companion command + report content |
-| Coder | `/40-Implement` | workflow + specialist agents |
-| QA | `/50-Verify` | workflow + QA/test skills |
-| Follow-up | `/10-Define` or `/30-Plan` ของรอบใหม่ | stage reuse, not separate numbered mainline |
-| GitHub review | `/50-Verify`, `/70-Release` | workflow/agent support |
-| MCP tool validation | `/50-Verify` | tool-specific verification skill |
-
-## Borderline Rules
-
-| Idea | Route | Keep as | Rule |
-| :--- | :--- | :--- | :--- |
-| Validation fixer | `/50-Verify` แล้วค่อยย้อน `/40-Implement` ถ้าต้องแก้โค้ด | thin skill/process note | ให้ verification ชี้ failure ก่อนเสมอ |
-| Documentation ideation | `Brainstorm`, `Wiki`, `/60-Report` | skill-backed support | ไม่ต้องเปิด mainline ใหม่ |
-| Performance ideation | `/50-Verify` หรือ `/40-Implement` เมื่อมีหลักฐาน | specialist skill/agent | ต้องมี measurement |
-| Security ideation | `/50-Verify` หรือ `Debug` เมื่อมี incident symptom | specialist skill/agent | treat as finding-first |
-| Follow-up planning | `/10-Define` -> `/20-Spec` -> `/30-Plan` ของรอบใหม่ | mainline reuse | ไม่แยก workflow หมายเลขใหม่ |
-| Legacy dashboard orchestration | legacy note only | migration-only | ไม่ใช้เป็นแบบตั้งต้นของ DevFlow 2.0 |
-
-## Follow-Up Planning
-
-เมื่อผู้ใช้ต้องการต่อยอดงานเดิม:
-
-1. อ่าน stage artifacts ที่มีอยู่ของ running ID เดิม
-2. ระบุให้ชัดว่าอะไร lock แล้ว และอะไรจะเพิ่มใหม่
-3. เริ่มรอบใหม่จาก `/10-Define` ถ้าโจทย์เปลี่ยน หรือ `/30-Plan` ถ้า spec ยังใช้ได้
-4. ใช้ไฟล์ `.md` ของ stage ใหม่เป็นหลักในการบันทึกบริบท
-
-## Output Principle
-
-เมื่อ prompt family ถูกแปลงเข้าระบบ:
-
-1. อย่า copy contract เดิมเข้ามาตรง ๆ
-2. แปลงให้สอดคล้องกับ numbering rule ของ DevFlow 2.0
-3. อย่าทำให้ผู้ใช้ต้องเดาเลขย้อนกลับ
-4. ให้ mainline มีเฉพาะ state ของงาน
-5. ให้ความสามารถเสริมไปอยู่ใน skill, agent, หรือ companion command ตามความเหมาะสม