원클릭으로 Manus에서 모든 스킬 실행

bc-setup-wizard-generator

스타16

포크5

업데이트2026년 4월 1일 16:56

Generates assisted setup wizard pages for Business Central setup tables following Guided Experience patterns. Creates NavigatePage with step-based navigation using visibility controls, banner images (WIP/Finished from Media Repository), temporary source table, footer actions (Back/Next/Finish with InFooterBar), OnOpenPage trigger (InitRecord, EnableControls, LoadSetupBanner), OnQueryClosePage trigger with unsaved changes confirmation, navigation procedures (NextStep with Step Option variable, EnableControls with Case statement, SetControlsStepXX boolean updates), commit procedure using TransferFields pattern, and registration codeunit with OnRegisterAssistedSetup event subscriber for Guided Experience. Integrates with Assisted Setup page and Extension Management. Supports multi-step workflows with welcome step, configuration step(s), and review/finish step. Uses InstructionalText for user guidance. Completes setup via GuidedExperience.CompleteAssistedSetup. Use when creating setup wizards, implementing assist

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

fernandoartalf

fernandoartalf/AL-Copilot-Skills-Collection

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

소프트웨어 개발자컴퓨터 및 수학직·SOC 15-1252

파일 탐색기

4 개 파일

SKILL.md

readonly

이 저장소의 다른 Skills

같은 저장소

documentation-bc-analysis-generator

fernandoartalf/AL-Copilot-Skills-Collection

Create well-structured Business Central feasibility analysis documents in the `openspec/analysis/` folder as the AL Analyst's working artefact backing a CCN, following the ANALYSIS-001 template structure. Captures references to the source user story / spec / CCN, change summary, scope & impact (objects added/modified, LoC, ID range usage), phased time estimate (Optimistic / Expected / Pessimistic with contingency and calendar duration), cost estimate at a stated EUR/h rate with assumptions, SWOT analysis (Strengths / Weaknesses / Opportunities / Threats), numbered risk register (`R-NN` with Likelihood / Impact / Mitigation), and a clear GO / NO-GO / CONDITIONAL-GO feasibility recommendation with non-blocking advisories and a handoff statement back to the Architect. Writes the file as `ANALYSIS-NNN-<kebab-title>.analysis.md` with frontmatter linking back to its spec, user story, and CCN. Use whenever the user asks to create, draft, generate, or write a feasibility analysis, ANALYSIS document, cost/time estimat

2026-06-0916

documentation-bc-architecture-generator

fernandoartalf/AL-Copilot-Skills-Collection

Create well-structured Business Central architecture documents in the `openspec/architecture/` folder as the long-lived companion to an existing approved technical spec, following the ARCH-001 template structure. Captures business and technical context, architectural drivers traced back to user-story ACs, numbered Architecture Decision Records (ADR-N) with Context/Decision/Consequence/Alternatives-rejected, a logical component view (ASCII or mermaid), key runtime flows, data architecture (entity-relationship + storage/ownership/key-derivation tables), cross-cutting concerns (security, reliability, performance, observability, localisation, RapidStart/portability, upgrade/migration), coexistence with legacy code, and known constraints/limitations. Writes the file as `ARCH-NNN-<kebab-title>.architecture.md` with frontmatter linking back to its spec, user story, and CCN. Use whenever the user asks to create, draft, generate, or write an architecture document, ARCH document, ADR, design rationale, or technical com

2026-06-0916

documentation-bc-ccn-generator

fernandoartalf/AL-Copilot-Skills-Collection

Create well-structured Business Central Change Control Notes (CCN) in the `docs/ccn/` folder (or `docs/<lang>-ccn/` for non-English variants) as the single stakeholder-facing artefact consolidating an approved user story, technical spec, architecture document, and feasibility analysis, following the CCN-001 template structure. Produces a single markdown file with consistent, ordered sections (Header, Business Context, Proposed Solution, Architecture, Feasibility, Time/Cost, Testing Setup, Testing Steps, Recommendation, Approvals) so the output can later be fed into the `md-to-docx-converter` skill with a placeholder template. Drives a short interview to capture (1) whether financial cost data must be included, (2) whether time/effort data must be included, (3) which estimate scenario(s) from the analysis to surface (Optimistic / Expected / Pessimistic / Neutral), and (4) the target content language as a BCP-47 code (`en`, `es`, `fr`, `de`, `it`, `pt`, `nl`, ...) into which all prose, table cell values, and bu

2026-06-0916

documentation-bc-md-to-docx-converter

fernandoartalf/AL-Copilot-Skills-Collection

Convert markdown documents to professionally formatted Word (.docx) files using Python and python-docx. The skill parses the markdown into sections, creates a JSON file with all section values, then substitutes Placeholder tokens in a Word (.docx/.dotx) template with the JSON values. Mermaid diagrams emitted by the `documentation-bc-ccn-generator` skill as DIAGRAM-mermaid marker blocks are rendered to PNG via the Mermaid CLI (mmdc) and inserted inline at the corresponding location in the docx. Use when user requests to convert markdown to Word, create a docx from markdown, generate a release note document, export markdown as Word, or apply template to markdown conversion. Trigger phrases include convert markdown to docx, export md to Word, generate release note from markdown, create Word document from markdown, convert to docx with template, apply template to markdown, or when working with markdown files that need to be delivered as formatted Word documents.

2026-06-0916

documentation-bc-phase-plan-generator

fernandoartalf/AL-Copilot-Skills-Collection

Create the full set of per-phase implementation plan files in the `openspec/plans/` folder from an approved Business Central technical spec, following the PLAN-PHASE template structure. For each phase listed in the spec's §8 Phase Overview, generates one `SPEC-NNN-phase-<N>-<phase-name>.plan.md` file with frontmatter (id, title, version, spec, user_story, ccn, phase, status, estimated_hours, branch, depends_on, related_docs, assignee, created_date, approved_date), and the mandatory body sections (References, Goal, Branch, Tasks as checkbox list each citing the AC it satisfies, Exit criteria, Out of scope for this phase, Notes for the AL Developer, Dependencies linking prerequisite phases and downstream consumers, Testing notes). All phases are generated in a single invocation so the developer has the full execution backlog after spec approval. Use whenever the user asks to create, draft, generate, or write phase plans, implementation plans, phase breakdown, plan files, task plans, or a development backlog for

2026-06-0916

documentation-bc-release-note-generator

fernandoartalf/AL-Copilot-Skills-Collection

Create well-structured Business Central release notes in the `docs/releasenotesmd/` folder from an approved spec, change-control note (CCN), or set of merged AL changes. Produces a single markdown release note with frontmatter (id, title, version, status, clientName, ccnNumber, issueNumber, releaseDate, releasedBy, module, createdDate, approvedDate), a fixed set of sections (Release Summary, Scope of Change, Change Request Details, Testing Setup, Testing Steps, Known Limitations, Approvals), and a sibling `*.releasenote.json` field map for downstream consumption by the `md-to-docx-converter` skill. No company, client, or publisher values are hardcoded — every identity field is either supplied by the user or read from the workspace `app.json`. Use whenever the user asks to create, draft, generate, or write a release note, RN, deployment note, change-request release document, or anything matching phrases such as "create release note", "draft release note for [client]", "generate RN from spec", "create release n

2026-06-0916

name

bc-setup-wizard-generator

description

BC Setup Wizard Generator

Automates creation of assisted setup wizards for Business Central setup tables following Guided Experience patterns.

Overview

Generates complete NavigatePage setup wizards with step-based navigation, banner images, temporary records, and Guided Experience registration. Follows Microsoft patterns for assisted setup.

Complete code templates available in: references/code-templates.md

Prerequisites

AL workspace with setup table
Setup table with fields to configure
(Optional) Setup page for post-wizard access

Workflow

Step 1: Gather Information

Collect from user:

Setup entity name (e.g., "Statistical Account")
Setup table name and ID
Prefix (e.g., "BCS")
Number of configuration steps (typically 2-4)
Field groups per step
Documentation URLs (video + written)

Step 2: Plan Wizard Steps

Define wizard structure:

Step 1: Welcome - InstructionalText explaining wizard purpose
Step 2-N: Configuration - Field groups by logical category
Final Step: Review & Finish - Read-only summary of all settings

Example 3-step wizard:

Welcome
Attachments Settings (Step 1/2)
Number Series Setup (Step 2/2)
Review & Finish

Step 3: Create Wizard Page

Create NavigatePage with:

PageType = NavigatePage
SourceTable = [Setup Table]
SourceTableTemporary = true ← Critical for unsaved workflow

Location: src/Page/[Prefix][Entity]SetupWizard.Page.al

See code-templates.md for complete structure.

Step 4: Add Banner Groups

Add two banner groups at top of layout:

SetupWIPBanner: Visible during configuration steps
SetupFinishedBanner: Visible on review/finish step

Uses Media Repository records:

AssistedSetup-NoText-400px.png (WIP)
AssistedSetupDone-NoText-400px.png (Finished)

See code-templates.md for complete code.

Step 5: Add Step Groups

Create one group per step with:

Visible property bound to StepXVisible boolean
InstructionalText for welcome/review steps
Field groups for configuration

Critical: Use step counters in captions for user guidance:

Caption = 'Attachments Settings 📎(Step 1/3)'

See code-templates.md for complete patterns.

Step 6: Add Navigation Actions

Add three actions in area(Processing):

ActionBack: Enabled = BackActionEnabled, calls NextStep(true)
ActionNext: Enabled = NextActionEnabled, calls NextStep(false)
ActionFinish: Enabled = FinishActionEnabled, calls FinishAction()

All have InFooterBar = true for bottom positioning.

See code-templates.md for complete code.

Step 7: Add Page Triggers

OnOpenPage:

Initialize temporary record from actual setup table
Call EnableControls() to show first step
Call LoadSetupBanner() to load banner images

OnQueryClosePage:

If FinishedProcess = true: Commit changes, mark setup complete
Else: Confirm user wants to exit without saving

See code-templates.md for complete implementation.

Step 8: Add Navigation Procedures

Create local procedures:

ResetControls(): Reset all visibility booleans and action states

NextStep(Backwards: Boolean): Increment/decrement Step option, call EnableControls()

EnableControls(): Case statement routing Step to SetControlsStepXX()

SetControlsStepXX(): Set visibility for specific step, enable/disable actions

See code-templates.md for complete code.

Step 9: Add Data Management Procedures

InitRecord():

Check if setup record exists
Create temporary record from existing or initialize new

CommitRecord():

Transfer temporary record to actual setup table
Insert if new, Modify if exists

FinishAction():

Set FinishedProcess = true
Close page (triggers OnQueryClosePage commit)

See code-templates.md for complete code.

Step 10: Add Setup Banner Loading

LoadSetupBanner():

Get Media Repository records by name
Get Media Resources by reference
Set BannersVisible if media has value

See code-templates.md for complete code.

Step 11: Declare Variables

Declare variables:

Record variables: Setup table, Media Repository (2), Media Resources (2)
Codeunit: GuidedExperience
Boolean: StepXVisible (per step), BackActionEnabled, NextActionEnabled, FinishActionEnabled, FinishedProcess, BannersVisible
Option: Step with values matching step groups

See code-templates.md for complete list.

Step 12: Create Registration Codeunit

Create codeunit with event subscriber:

Subscribe to Codeunit::"Guided Experience"::OnRegisterAssistedSetup
Call AssistedSetup.InsertAssistedSetup() with:
- Title and description labels
- Time estimate (minutes)
- Wizard page ID
- Assisted Setup Group
- Video URL and category
- Documentation URL

Location: src/Codeunit/[Prefix][Entity]SetupManagement.Codeunit.al

See code-templates.md for complete code.

Step 13: Build and Test

Build project: al_build
Publish: al_publish
Test from:
- Assisted Setup page (search "Assisted Setup")
- Extension Management (Setup actions)
Verify:
- Navigation works (Back/Next/Finish)
- Banners display correctly
- Exit confirmation on close without finish
- Changes saved on finish
- Completion check marked

Troubleshooting

Wizard doesn't appear in Assisted Setup

Cause: Event subscriber not firing or registration failed
Fix: Check OnRegisterAssistedSetup event subscriber syntax, verify codeunit compiles without errors

Banners don't display

Cause: Media Repository records not found or media reference empty
Fix: Check exact image names (AssistedSetup-NoText-400px.png, AssistedSetupDone-NoText-400px.png), verify Media Repository exists in base BC

Changes saved even when clicking X to close

Cause: OnQueryClosePage not checking FinishedProcess flag
Fix: Ensure if FinishedProcess then condition exists, verify FinishAction sets flag before CurrPage.Close()

Steps don't navigate forward/backward

Cause: Step option enum values don't match group names, or EnableControls case statement incomplete
Fix: Verify Step option has value for each step (Step10, Step20, Step30, etc.), check Case statement includes all values

Error on finish: "Record already exists"

Cause: CommitRecord trying to Insert when record exists
Fix: Check if not SetupRecord.Get() then Insert else Modify pattern in CommitRecord procedure

Setup marked complete but changes not saved

Cause: CommitRecord not called before CompleteAssistedSetup
Fix: Ensure OnQueryClosePage calls CommitRecord() before GuidedExperience.CompleteAssistedSetup()

Review step shows editable fields

Cause: Review step groups missing Editable = false property
Fix: Add Editable = false to all field groups in final review step

Quick Reference

Snippet: Use Waldo's tpagewizard3stepswaldo snippet for rapid scaffolding

Core Pattern: Temporary record → User edits → Finish commits → Mark complete

Key Properties:

Page: PageType = NavigatePage, SourceTableTemporary = true
Actions: InFooterBar = true
Groups: Visible = StepXVisible

Required Codeunits: Guided Experience (InsertAssistedSetup, CompleteAssistedSetup)

Media Files: AssistedSetup-NoText-400px.png, AssistedSetupDone-NoText-400px.png