agent-taskboard-manifest

Name: agent-taskboard-manifest
Author: jinzhezenggroup

113stars23forks

How to install agent-taskboard-manifest?

jinzhezenggroup/computational-chemistry-agent-skills/agent-taskboard-manifest

$npx -y skills add jinzhezenggroup/computational-chemistry-agent-skills --skill agent-taskboard-manifest

Installs into the current project.

Summary

It is a specification for semantic workflows used by agents to plan, generate, formalize, summarize, and execute complex tasks, projects, experiments,and research efforts for agents, requiring explicit structure, lazy loading,scoped context, evidence-grounded routing, and human r

Files · 1

View on GitHub

SKILL.md

1	# Agent Workflow Specification (AgentTaskboardManifest)
2
3	## Execution Procedure
4
5	It is mandatory for the Agent to read `./reference/syntax_and_semantics.md` as the definitive source of truth prior to evaluating task routes, interpreting user intent, or generating any workflow artifacts.
6
7	After establishing this foundation, the Agent must determine the applicable execution route and strictly execute the corresponding standard operating procedures:
8
9	### Route 1: Planning / Generation
10
11	Applies when building a new workflow from scratch collaboratively.
12
13	- Core Planning Constraints:
14	- No Execution Allowed: The planning phase is strictly for structural modeling. Executing operations, running commands, or validating the environment is strictly prohibited (these actions belong exclusively to the execution phase).
15	- Skill Priority: When formulating strategies, always prioritize solutions supported by existing Agent Skills over custom script generation or manual tool creation.
16
17	1. Mandatory Reading: `./reference/plan_communication_guidelines.md`.
18	1. Mandatory Reading: `./reference/design_guidelines.md`.
19	1. Initial Alignment & Baseline: Engage with the user to outline the strictly macro-level structure. Produce the minimum baseline deliverables (`-workflow.yaml` and `!entry.task.yaml`). Do not delve into any execution details, concrete parameters, or deep sub-tasks at this stage. Report the preliminary architecture to the user and wait for the user's confirmation.
20	1. Iterative Refinement: Progressively expand the workflow details and deep-level tasks through continuous user consultation. You must discuss and design only ONE specific sub-task at a time. Unfolding or generating the entire detailed workflow tree simultaneously is strictly prohibited. Strictly adhere to syntax and design constraints. Arbitrary fabrication of steps or dependencies is strictly prohibited.
21
22	### Route 2: Formalization / Summarization
23
24	Applies when converting a text plan into a manifest, or abstracting completed work into a reusable workflow.
25
26	1. Mandatory Reading: `./reference/design_guidelines.md`.
27	1. Context Processing & Abstraction:
28	- For text-based plans: Logically expand the provided details. Proactively query the user regarding any ambiguous logic, missing constraints, or edge cases. Use `unknown` for unverified parameters.
29	- For summarizing executed work: Extract and abstract hardcoded values into reusable variables. Separate run-specific instances from universal logic to ensure the resulting workflow is highly extensible, not a one-off script.
30	1. Finalization: Output the complete workflow strictly adhering to the syntax constraints. Generating unsupported operations or assuming user intent without confirmation is strictly prohibited.
31
32	### Route 3: Loading & Execution
33
34	Applies when directed to execute an existing workflow.
35
36	1. Pre-flight Check: Verify that the target workflow directory exists and is accessible. Read the `-workflow.yaml` to confirm its applicability and prerequisites against the current environment.
37	1. Mandatory Reading: `./reference/execution_guidelines.md`.
38	1. Strict Execution: Dynamically load tasks step-by-step, strictly starting from `!entry.task.yaml`. The Agent must rigidly follow the defined sequence, evaluate routing conditions based entirely on runtime evidence, and respect all defined human-in-the-loop breakpoints. Deviating from or hallucinating beyond the defined workflow path is strictly prohibited.

jinzhezenggroupPublisher · 39 listings

Preview

jinzhezenggroup/computational-chemistry-agent-skills

Repojinzhezenggroup/computational-chemistry-agent-skills

LicenseLGPL-3.0

TypeSkills

CategoryGeneral

UpdatedJul 2026

Repo stars113

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type

agent-taskboard-manifest

113stars23forks

View on GitHub

How to install agent-taskboard-manifest?

jinzhezenggroup/computational-chemistry-agent-skills/agent-taskboard-manifest

$npx -y skills add jinzhezenggroup/computational-chemistry-agent-skills --skill agent-taskboard-manifest

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Agent Workflow Specification (AgentTaskboardManifest)
2
3	## Execution Procedure
4
5	It is mandatory for the Agent to read `./reference/syntax_and_semantics.md` as the definitive source of truth prior to evaluating task routes, interpreting user intent, or generating any workflow artifacts.
6
7	After establishing this foundation, the Agent must determine the applicable execution route and strictly execute the corresponding standard operating procedures:
8
9	### Route 1: Planning / Generation
10
11	Applies when building a new workflow from scratch collaboratively.
12
13	- Core Planning Constraints:
14	- No Execution Allowed: The planning phase is strictly for structural modeling. Executing operations, running commands, or validating the environment is strictly prohibited (these actions belong exclusively to the execution phase).
15	- Skill Priority: When formulating strategies, always prioritize solutions supported by existing Agent Skills over custom script generation or manual tool creation.
16
17	1. Mandatory Reading: `./reference/plan_communication_guidelines.md`.
18	1. Mandatory Reading: `./reference/design_guidelines.md`.
19	1. Initial Alignment & Baseline: Engage with the user to outline the strictly macro-level structure. Produce the minimum baseline deliverables (`-workflow.yaml` and `!entry.task.yaml`). Do not delve into any execution details, concrete parameters, or deep sub-tasks at this stage. Report the preliminary architecture to the user and wait for the user's confirmation.
20	1. Iterative Refinement: Progressively expand the workflow details and deep-level tasks through continuous user consultation. You must discuss and design only ONE specific sub-task at a time. Unfolding or generating the entire detailed workflow tree simultaneously is strictly prohibited. Strictly adhere to syntax and design constraints. Arbitrary fabrication of steps or dependencies is strictly prohibited.
21
22	### Route 2: Formalization / Summarization
23
24	Applies when converting a text plan into a manifest, or abstracting completed work into a reusable workflow.
25
26	1. Mandatory Reading: `./reference/design_guidelines.md`.
27	1. Context Processing & Abstraction:
28	- For text-based plans: Logically expand the provided details. Proactively query the user regarding any ambiguous logic, missing constraints, or edge cases. Use `unknown` for unverified parameters.
29	- For summarizing executed work: Extract and abstract hardcoded values into reusable variables. Separate run-specific instances from universal logic to ensure the resulting workflow is highly extensible, not a one-off script.
30	1. Finalization: Output the complete workflow strictly adhering to the syntax constraints. Generating unsupported operations or assuming user intent without confirmation is strictly prohibited.
31
32	### Route 3: Loading & Execution
33
34	Applies when directed to execute an existing workflow.
35
36	1. Pre-flight Check: Verify that the target workflow directory exists and is accessible. Read the `-workflow.yaml` to confirm its applicability and prerequisites against the current environment.
37	1. Mandatory Reading: `./reference/execution_guidelines.md`.
38	1. Strict Execution: Dynamically load tasks step-by-step, strictly starting from `!entry.task.yaml`. The Agent must rigidly follow the defined sequence, evaluate routing conditions based entirely on runtime evidence, and respect all defined human-in-the-loop breakpoints. Deviating from or hallucinating beyond the defined workflow path is strictly prohibited.

jinzhezenggroupPublisher · 39 listings

Preview

jinzhezenggroup/computational-chemistry-agent-skills

Repojinzhezenggroup/computational-chemistry-agent-skills

LicenseLGPL-3.0

TypeSkills

CategoryGeneral

UpdatedJul 2026

Repo stars113

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type